OOT — Development Proposal

01 — Where we are

The design is finalized and signed off.

The complete UI/UX design for the OOT app is locked. Every screen, flow and interaction: onboarding, phone-code auth, trip creation, multi-destination itineraries, accommodation, invites, group chat, polls, expense split & settle-up, and the full OOT 2.0 visual system. The web admin panel runs on a standard dashboard layout, so it needs no separate design phase. With design complete, this proposal covers the development phase — building, integrating, testing and shipping OOT to the App Store, Google Play and the web.

Design ✓

UI/UX finalized & signed off

3 surfaces

iOS, Android & web admin

~8 wk

Estimated build to launch

Total development investment

Design is complete — this proposal is the build. The approved design system and clickable prototype are done. What follows is a clean development quote to turn that proven design into a shipping product across mobile and web, on one shared backend.

02 — What we're building

One place to plan the whole trip.

A collaborative trip-planning mobile app (iOS + Android), backed by a web-based admin panel and a shared backend — so a group can plan a trip together instead of losing it in the group chat.

React Native · iOS & Android Web admin panel Shared backend + API

Passwordless sign-in

Onboarding plus phone-number / one-time-code sign-in — no passwords to remember.

Create & invite

Create a trip, invite friends, add multi-city destinations with dates.

Collaborative itinerary

Shared itinerary, accommodation (with links & voting) and transportation.

Polls & voting

Accommodation chosen by majority, activities decided by votes.

Group chat

A group chat with in-line polls, right where the planning happens.

Expense split & settle-up

Splitwise-style: who owes whom, per-pair transactions, settle up.

Host controls & preview

Edit / "Planning" mode and host controls; a blurred preview for un-accepted invitees.

Make it yours

GIF / custom cover photos, profile, plus privacy, terms & contact.

Web admin panel

Run the platform from the web — full CRUD, active users and at-a-glance stats.

The product

The signed-off design, screen by screen.

A look at the OOT app you’ve approved — from the branded splash to planning, polls and settle-up. This is what we build, pixel-for-pixel, across iOS and Android.

Getting it out the group chatBranded splash & onboarding

Your trips, one tap awayHome dashboard

Build the itinerary togetherDay-by-day, grouped by location

Stay options, voted onAccommodation & voting

Chat & polls in one placeGroup chat with in-line polls

Split it, settle upSplitwise-style expenses

Make it yoursProfile & achievements

← swipe to explore the screens →

03 — Development milestones & investment

Four milestones, one clean quote.

Development runs in clear milestones — each delivered and approved before the next begins. Design (M1) is already complete; the figures below cover the build.

M1 Design

✓ Completed

UI/UX design + clickable prototype

The complete OOT design system, every screen and flow, and a clickable prototype — for the app. Done and signed off.

M2 Frontend Development

The app & admin panel, built

React Native build (iOS + Android) of all approved screens plus the web admin panel — the full OOT 2.0 design system, splash animation, components, navigation and state.

M3 Backend, API & Integration

The engine behind it

Backend, REST API and database; phone-code auth; the trip / collaboration data model, invites, polls and expense-split logic; admin-panel CRUD, active-users and stats; app ↔ admin ↔ backend on one shared backend.

M4 QA, Testing & Launch

Tested & shipped

A full QA pass and fixes, App Store and Google Play submission, and web deployment — OOT live across all three surfaces.

Total — Development

Across milestones M2, M3 and M4. M1 (design) is already complete.

How the investment breaks down

M2 — Frontend$1,500

M3 — Backend & API$1,200

M4 — QA & Launch$300

04 — The build, month by month

From kickoff to launch in ~8 weeks.

Three milestones across roughly two months, each delivered and approved before the next begins. These are actual development timelines — client feedback and fix cycles extend them, and any change to the approved design affects both the timeline and the cost.

Month 1 · Weeks 1–4

Month 2 · Weeks 5–8

M2 Frontend

Weeks 1–3 · Month 1

The app & admin panel, built

All approved app screens in React Native (iOS + Android)
Splash animation, components, navigation & state
Web admin-panel front-end

M3 Backend & Integration

Weeks 4–6 · Month 1–2

The engine behind it

Backend, REST API & database
Phone-code auth + collaboration logic — invites, polls, expense split
Admin CRUD, active users & stats
App ↔ admin ↔ backend, wired together

M4 QA & Launch

Weeks 7–8 · Month 2

Tested & shipped

Full QA pass & fixes
App Store + Google Play submission
Admin web deployment

★ Live

OOT, out the group chat 🚀

Shipped across iOS, Android and the web admin panel — one shared backend, ready for real trips.

05 — Payment & scope

Milestone-based, and clear about scope.

Simple, predictable payments through Fiverr — and a clean line around what's included, so the build stays on time and on budget.

Payment

Milestone-based, via Fiverr. Each milestone is placed as an order and begins on confirmation; the next starts once the prior is delivered and approved.

M2 — Frontend Development$1,500
M3 — Backend, API & Integration$1,200
M4 — QA, Testing & Launch$300
Total — Development$3,000

Scope & change requests

This proposal delivers development of the approved, signed-off design. Everything in the locked design — every screen, flow and interaction — is included in the milestones above.

Any new features, screens or flows beyond the locked design will be scoped and quoted as a separate change request before work begins — so the build stays on time and on budget.

06 — Terms

Clear terms, no surprises.

A few terms so we're aligned on timeline, scope and how we work together.

The timeline reflects actual development time. Client feedback and fix cycles extend it, and any change to the approved design affects both timeline and cost — scoped and quoted as a separate change before work begins.

Scope & working terms

Scope & changes. Any change in scope or price is set out in a separate written quote, agreed by both sides, before work begins.

Timeline. Estimates are actual development time; client feedback and fix cycles extend the schedule.

Independent contractor. TX Dynamics is engaged as an independent development firm for the design, development and deployment of the app.

Commercial & legal

Invoicing & currency. Invoices are issued and paid in USD, via Fiverr.

Ownership. Copyright over the final product transfers to the client on final payment; TX Dynamics may showcase the work in its portfolio.

Confidentiality. Information exchanged between TX Dynamics and the OOT team stays confidential and is used only for this project.

Entire agreement & severability. This proposal is the full agreement for the development project; if any term is unenforceable, the rest remains in force.

07 — Next step

How we kick off.

Approve the proposal

Confirm the milestones and investment above.

Formal contract

Once the proposal is agreed, we share a formal contract to sign before kickoff.

Place the M2 (Frontend) order

That kicks off development — we start building the app and admin panel against the approved design.

Weekly progress

We share progress on the agreed weekly cadence as the build comes together.

Milestone to milestone, to launch

Each milestone delivered and approved in turn, through to App Store, Google Play and web.

Reach out on Fiverr to kick off M2 Questions? Reach out to the team on Fiverr.