Brain AnalyticaBrain Analytica
Approve
Phase 3 Dashboard
Future PhaseBudgetary Estimate
Dependency

Phase 2 accounts & booking API live.

What this unlocks

In-journey traveler engagement, push notifications, and higher retention.

P3
Mobile Application MVP

Mobile Application MVP

Meet travelers on their phone before, during, and after the trip.

Investment
EGP 600K - 750K (indicative)
Fourth - after booking stabilizes in web
Duration
10-14 weeks
Complexity · High
Business Value
Technical Complexity
Operational Impact
Dependencies
Phase 2
Risk Level
Medium-High
Enables
Phase 4Phase 5
Key Deliverables
  • iOS & Android apps
  • Shared customer account
  • Mobile booking
  • Push notifications
  • Maps & nearby discovery
Pricing for Phases 2-7 is preliminary, non-binding, and subject to discovery, approved scope, integrations, timeline, and commercial validity. Excluding applicable VAT and third-party operational fees.
Section 01 · Rationale

Why this phase exists

The Problem

Mobile is where travelers plan, book, and use the service - a web-only experience loses reach and retention.

The Context

Phase 3 ships iOS and Android apps that share the customer account, booking, notifications, and support systems.

If Skipped

No push channel, no on-trip experience, no nearby discovery - the brand disappears once the traveler leaves the site.

Section 02 · Impact

Business value created

Native Apps
iOS + Android
↑
Shared codebase
Push Channel
Live
↑
Direct to traveler
Nearby Discovery
Enabled
↑
Maps + geo
Retention
+High
↑
App presence
Section 03 · Scope

What will be built

AU
Shared Account

Same login as web.

Unified identity
BK
Mobile Booking

Full booking on device.

Mobile revenue
MT
My Trips

Documents & timelines.

On-trip utility
PN
Push Notifications

Trip & marketing.

Free channel
MP
Maps

Locations & routing.

In-destination help
ND
Nearby Discovery

Geo-based content.

Upsell moments
SV
Saved Items

Wishlist & compare.

Return intent
SU
Support Center

Complaints, cancellations.

Trust
Section 04 · Systems

How it connects

Phase 3 · System Architecture
Mobile App
iOS
Android
Booking API
Push Service
Maps Provider
Media CDN
→ AI Planner
→ Content System
Channel System Data Future
Section 05 · Delivery

Timeline & milestones

  1. Weeks 1–2Design
    Mobile UX & prototypes
  2. Weeks 3–7Build
    Cross-platform build
  3. Weeks 4–8Backend
    Push, maps, geo backend
  4. Weeks 9–11Build
    My Trips & support
  5. Weeks 12–13QA
    Device QA & store prep
  6. Week 14Launch
    Store submission & launch
Section 06 · Effort

Indicative engineering effort distribution

Phase 3 · Effort Distribution
Not accounting percentages - indicative distribution of engineering effort across disciplines.
Section 07 · Complexity

Project complexity profile

Business Logic
70
Backend
60
Frontend
60
Mobile
95
Integrations
75
Testing
85
Security
75
Scalability
70
Section 08 · Risks

Risks & dependencies

Technical
  • Store review cycles
  • Push provider limits
  • Device fragmentation
Scope
  • Native features scope creep
Client
  • Store accounts readiness (Apple, Google)
Section 09 · Definition of Done

Success criteria

Apps published on both stores
Booking parity with web
Push notifications delivering
Maps & nearby discovery functional
Section 10 · Roadmap

What this unlocks next

Next Phase

Phase 4 - AI Planning & Personalization

Reused

Mobile becomes the primary AI surface - chat, itinerary, recommendations in-hand.

Unlocks

Personalized planning where travelers already are.

Navigate Phases
Previous
Phase 2 · Structured Booking Platform
←
Next
Phase 4 · AI Planning & Personalization
→
Back to Investment Overview
↗
Full Roadmap
↗