المنيو
تصفّح أطباق ومشروبات حبق مع أسعارها، اختر اللي بتحبه، وأرسل طلبك على واتساب.
اطلب الآنThis document specifies a mobile café application for كافيتيريا ومطعم حبق, a local café and restaurant. The product intent, derived from the requester's instruction, is to give the café a single mobile app that presents its full offering — products, prices, location, and phone number — and provides action buttons, including a reservation button, with orders delivered to WhatsApp. The requester asked for a comprehensive treatment of everything the café's Google Maps listing contains, analyzed and carried into the app.
The audience is the café's guests: families and young guests in a friendly local setting who want to see what the café serves, what it costs, where it is, how to call it, how to reserve a table, and how to send an order straight to the café's WhatsApp.
The authoritative content source is the café's Google Maps listing (https://maps.app.goo.gl/xwdNMUWtFTxyd4kx8). The listing could not be retrieved programmatically during analysis (Google Maps access restrictions), so the specific menu items, prices, street address, and phone number are not verified facts in this document. The app is specified to display them from a single café data source that the café supplies; no menu item, price, address, or phone number is invented here. See Section 2b and Section 11.
The product is a mobile-first café app with four destinations — Landing, Menu, Contact, and Reservation — all reachable without an account. The café customer browses the menu with prices, checks the café's location and phone number, starts a table reservation from a reservation button, and sends an order to the café's WhatsApp. WhatsApp is an external recipient: the app composes the order message and hands it to WhatsApp; the app does not process, accept, or track the order itself.
Current delivery comprises a React frontend, a shared FastAPI backend serving the application APIs and domain modules, and a MariaDB database holding the café's application-owned data (menu items, prices, café contact and location details, and reservation requests). No customer account, login, or profile exists.
Removed from scope
The app is a first-party mobile application owned by the café. All four destinations are public and anonymous: a customer opens the app and immediately sees the café's offering without registering, signing in, or providing identity. There is no account lifecycle, no customer profile, and no stored customer history.
The café's factual content — products, prices, location, and phone number — is application-owned data served by the backend and rendered by the app. Because the Google Maps listing could not be read during analysis, this content is modeled as café-supplied data with a defined shape (Section 2c, Menu and Contact) rather than as invented values; the café's real listing values populate it.
Two boundaries are external and stay external:
Reservations are initiated in the app and recorded as reservation requests in the café's own database so the request is not lost when the customer leaves the app; the app shows the customer the request state it can truthfully observe. Nothing beyond these boundaries — no payment, no delivery tracking, no loyalty program, no table-availability engine — is part of current delivery.
The reference directive for https://maps.app.goo.gl/xwdNMUWtFTxyd4kx8 declares content_source with authoritative instruction: "Use the café listing data: products, prices, location and phone number."
Verified source observations returned an access error: the Google Maps URL could not be retrieved due to access restrictions. Consequently no listing item, price value, address string, or phone number could be verified, and none is fabricated here. The inventory is therefore the verified business identity only, plus the required content slots that the café's listing must fill:
35.013599, longitude 37.051082FR-1 — Products with prices. As a café customer, I should see the café's products with their prices so that I know what is served and what it costs. (explicit)
FR-2 — Café location. As a café customer, I should see the café's location so that I can find it. (explicit)
FR-3 — Café phone number. As a café customer, I should see the café's phone number so that I can call it. (explicit)
FR-4 — Action buttons including reservation. As a café customer, I should have action buttons, including a reservation button, so that I can act on what I see. (explicit)
FR-5 — Order sent to WhatsApp. As a café customer, I should send my order to the café's WhatsApp so that the café receives it. (explicit)
FR-6 — Content from the café listing. As a café customer, I should see content that comes from the café's Google Maps listing — كافتيريا ومطعم حبق — so that the app reflects the real café. (explicit)
FR-7 — No-account entry. As a café customer, I should open the app without an account so that I can use it immediately. (required_inference)
FR-8 — Customer sends the order to WhatsApp. As a café customer, I should complete the WhatsApp handoff myself so that the order reaches the café under my control. (required_inference)
FR-9 — Reservation request recorded. As a café customer, I should submit a reservation request and see that it was recorded so that I know my request was not lost. (required_inference)
The creative direction — sensual pop minimalism for a warm café, after Karim Rashid — is authoritative for this section.
#FFF4EC#FFFFFF#221A2B#E85C8A#B6E33B#7A6E80clamp() from 34px mobile to 64px desktop for the hero headline.The public entry — Landing — is a full-width bubblegum-pink band (#E85C8A) with a large rounded blob on the right holding one glossy lime (#B6E33B) blob that drifts slowly behind the café name. The café name "حبق" sits left in bold Comfortaa at 64px desktop / 34px mobile, with the headline "حبق: قهوة وطعام قريب منك" and subline "شوف المنتجات والأسعار، احجز طاولتك، وأرسل طلبك على واتساب." beneath it. A capsule "اطلب الآن" button sits below the name, and the band's lower edge curves into the cream (#FFF4EC) block below with a 40px radius. The concept recomposes only accepted content and controls: the hero copy, the order CTA leading to Menu, and the reservation capsule leading to Reservation.
Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: layered_2d
Landing Hero Motion Brief
prefers-reduced-motion, a usable static arrangement is provided; the single hero loop stops.docker-compose.yml with the three provisioned services — frontend, backend, database — with the frontend reaching the backend API and the backend reaching MariaDB.
شوف المنتجات والأسعار، احجز طاولتك، وأرسل طلبك على واتساب.
تصفّح أطباق ومشروبات حبق مع أسعارها، اختر اللي بتحبه، وأرسل طلبك على واتساب.
اطلب الآنشوف مكان الكافيتريا على الخريطة واتصل فينا مباشرة من التطبيق.
احجز طاولتك قبل ما تجي وخلّي جلستك جاهزة مع العيلة أو الأصحاب.
احجز طاولة
شوف المنتجات والأسعار، احجز طاولتك، وأرسل طلبك على واتساب.
تصفّح أطباق ومشروبات حبق مع أسعارها، اختر اللي بتحبه، وأرسل طلبك على واتساب.
اطلب الآنشوف مكان الكافيتريا على الخريطة واتصل فينا مباشرة من التطبيق.
احجز طاولتك قبل ما تجي وخلّي جلستك جاهزة مع العيلة أو الأصحاب.
احجز طاولة
No comments yet. Be the first!