EQ Ventures · SOW SST-EQ-011 · AWS proof of concept
One app. Three roles.
Clickable wireframes for the Coralis Island destination super app. The visitor and
partner sides are the same mobile app seen through two different sign-ins; the
EQ Ventures — the platform operator — works in a web console that governs every
country and destination on the network. Everything here runs from one deployment and
one database.
The demonstration path. A visitor signs in, picks the destination the office
has opened, and the map, listings, zones and currency all load from that place. They
browse — or they ask the AI Trip Advisor for a day-by-day plan, built only from
businesses inside the destination boundary, each one linked straight into its booking
flow. They select, book, and pay at checkout: a QR payment code is the default
method, card and wallet are working mocked flows in the same interface. The partner
sees the booking in their inbox and the administrator sees it in the console — the whole
loop, in under a minute, across three devices.
Connected mode, live GPS. Every map, distance and route is computed from the
device's live position. Offline capability, live settlement and the safety module are out
of scope for this engagement — they are not built here and they are not mocked.
Multilingual by construction. No label is written into a screen. Every string
carries a key and resolves through a translation table at render time, so a new language
is a new column — not a new build. Try the language chips on the visitor splash screen;
Arabic flips the layout to right-to-left.
37Screens
3Roles
2Console roles
2 × 2Countries × destinations
5Languages, one build
11Core entities
🧭
Visitor
Mobile app · 18 screens
Opens straight into onboarding — pick a language, 5 shipped including right-to-left
Register with basic details only — name, email, password, language
Sign in, then choose a country and a destination the office has opened
The map, listings, zones and currency all load from that place
Home feed, 8 categories and the business directory
Interactive island map with business and landmark pins
AI Trip Advisor — free text in, a day-by-day plan out, every item a real listing
Guardrails: nothing invented, nothing outside the destination boundary
Book a stay, table or activity — instant or on request
Checkout with a QR payment code as the default method; card and wallet mocked
Confirmation with a check-in code, trip map on live GPS, notifications
🏪
Partner
Mobile app · 12 screens
Partner sign in and application to join the destination
Search the map and drop a pin on your exact location
Awaiting approval — draft a listing, but publish nothing
Category confirmed by the office — it decides where visitors find you
Listings and services, with a price on each
Availability: open, closed, or capacity for a given day
Booking inbox — accept or decline; today's arrivals
Earnings summary — confirmed bookings and booking value per listing, each showing the commission its category charges
🖥️
EQ Ventures
Web console · 8 sections · two console roles
Two roles in one console — a super admin runs the whole network; an admin runs the country they were given
Sign in with email and password only — the account carries its own role, so there is no role picker to get wrong
Super Dashboard — create admin accounts, scope each to a country or leave them network-wide, reassign later
Secure login, then a network dashboard covering every country at once
Filter everything by country, destination or area — one control, all screens
Break bookings and partners down by any of the four groupings
Visitors, each with their booking history
Business registry — approving a partner means confirming its category, which is also what decides the commission it pays
Every category carries one published rate — the number a business is shown before it applies, on Categories & commission
Only a super admin may change a rate: on the category, or for one business at approval. An admin sees it and approves on it
Every booking, with how it was paid — QR, card or wallet
Destinations & setup — super admin only: one card per country, and inside it every destination placed on the map
Add a country from a searched list, then add a destination to it: pin it on the map or paste lat/long, with a radius, currency and language
Categories & commission on its own page — what browse, filters and the Trip Advisor use, and what each category charges
Announcements to all app users
In this POC — what these wireframes show
Browse, map, book and my trips. The AI Trip Advisor on Amazon Bedrock.
Checkout with QR payment as the default method, card and wallet as working
mocked flows. Listings, availability, a booking inbox, arrivals and an earnings
summary. Approvals with commission set per business, registries, booking oversight,
content and announcements, and a super admin who creates the admins. Two
differently branded destinations from one deployment, switched by configuration alone.
Not in this engagement — subsequent phases
Live settlementPayoutsRefunds & reconciliationPCI-DSSOffline modeSafety & SOSSMS fallbackKnowledge base / vector retrieval
Each is an additive change to the same data model, not a rebuild. Nothing on this
list is mocked in the prototype.
Console logins: super admin ayyub@eq.com · admin amara@eq.com — both coralis·Switch roles with 1234·Resize the phone with +−,
0 to fit·Reset returns a prototype to its first screen