FlutterFlow Mobile App Front-End Development

Job ID: 40341754

Budget: £250 – £750 GBP

I'm looking for an experienced FlutterFlow developer to build the front-end of a mobile app — Phase 1 only, fixed price.
The backend already exists and is being handled separately, so this is a pure front-end job: 10 pages, clean navigation, reusable components, placeholder data, and a well-organised project ready for a second contractor to continue into Phase 2. No backend hookup, no API calls, no payment setup — that's all out of scope for now.

What I need built:

Ten pages in total: Splash, Onboarding, Pricing, Login/Sign Up, Upgrade/What You Get, Home, History, Detail, Progress, and Account.
The layout should be mobile-first, with sensible tablet and web adjustments throughout. All pages should be linked and navigable, with reusable components built cleanly so they can be extended later. Placeholder and sample data only — no live data connections at this stage.

A few pages worth calling out:

The Detail page is the most important one. It needs to show a source/title, date, overall score, a friendly opening summary, and an item-by-item breakdown — with a coloured indicator next to each item, a short note beneath it, and a summary section at the bottom. Longer results should have a "See more" behaviour rather than dumping everything on screen at once.
The Home page should show the latest overall result, a progress snapshot, the top recommendations from the latest review, and two clear calls to action: view the latest full review, and see all previous entries. It also needs a clean empty state for first-time users.
The Progress page needs a score chart area and a grouped totals section — polished layout preferred if time allows.
The Account page should cover: current plan, usage allowance, upgrade/change plan, cancel plan, update password, contact us, and logout.

The handover is as important as the build:

I'll be handing this project to another developer for Phase 2, so cleanliness matters a lot. I need every page and component named clearly and logically, placeholder widgets left exactly where real data will slot in later, and a short handover sheet that tells the next developer things like:

This text should bind to friendly_message
This list should bind to items_json
This page should only show when status = processed
This score should use overall_score

Think of it as leaving the project in the state you'd want to find it in.

Design direction
The app should feel friendly, calm, and easy to navigate — the kind of thing that doesn't intimidate someone who's already a bit overwhelmed. Think clean and spacious, not clinical or over-designed. Avoid anything harsh, cluttered, or fussy.

Deliverables

Finished FlutterFlow Phase 1 project
All 10 pages built and linked
Reusable components throughout
Placeholder/sample data layouts
Mobile, tablet, and web responsive structure
Clear, consistent naming across the whole project
Short handover notes for Phase 2


When applying, please include:

Examples of previous FlutterFlow work
Confirmation you've built mobile-first projects with tablet and web adjustments
Confirmation you're comfortable working to a front-end-only scope
A note on how you approach clean handovers
Your realistic timeline
A fixed price for Phase 1 only


Happy to answer questions before you quote. Looking for someone who takes pride in leaving things tidy as much as getting them built.