Nestora — Flutter Real Estate UI Kit
A property browsing and viewing-booking app, finished down to the empty states.
The real app, compiled for the web and served from this site. It loads on click because it is a full Flutter build, not a video.
Nestora is the front end of a property app: someone browses listings, opens one, looks at the photos and the numbers, then books a time to see the place. Every screen in that path is built, themed and wired to mock services — you swap the service bodies for your API and the app keeps working.
It is deliberately not a loud commerce template. The palette is indigo-violet with a warm gold accent on a soft lilac-white ground, and every colour, radius and font size lives in one token file, so re-skinning it for a client is an afternoon, not a rewrite.
Run it in one minute
after download$ unzip nestora-v1.0.zip
$ cd realestate_ui_kit
$ flutter pub get
$ flutter run
No backend to stand up, no keys to obtain. The app runs on bundled mock data; the demo above is this exact build compiled for the web.
Then make it yours
two filesRe-theme from the token file
Colours, radii, spacing and fonts live in one place. Change them there and every screen follows.
Point the services at your API
3 mock services return Futures. Replace their bodies with HTTP calls; controllers and screens do not change.
What it looks like
9 screens








Who it is for
- You are building a property, rental or listings app and do not want to draw 21 screens first.
- You need something to show a client this week, running on a phone, with real photos in it.
- You want the plumbing (routing, state, loading and empty states) already decided so you can argue about features instead.
In the box
- Full Flutter source, no obfuscation, no license server
- GetX architecture: View → Controller → Service → Model, lazy bindings per route
- All demo data in one file; three mock services with Future signatures
- README with a re-theming walkthrough and an API integration guide
- Runs on iOS and Android from the same source
Features
- Full browse → detail → book-a-viewing path, including the viewing status timeline afterwards
- Map view with live price pins
- Listing detail with photo gallery, price, beds / baths / floor area, highlights and the listing agent
- Viewing slot picker — in person or video, with a preferred time
- Light and dark themes, both palettes in one file, runtime toggle
- Skeleton loaders and empty states already wired on every list
- Saved homes, address book with default-address handling, profile and settings
- Money formatting in pure Dart ($749,000); free viewings read Free
- Eight bundled royalty-free property photos, all rendered through one PropertyImage widget with a gradient fallback
Not included
- No backend, no admin panel, no database — this is the app layer
- No real map SDK key: the map view draws price pins over a static map image
- No payment, no push notifications, no analytics SDK
- Login and OTP are mock flows, not an auth service
- The bundled photos are demo assets, licensed for the demo — ship your own
The package has no paid dependencies. Fonts are Google Fonts (open licence) and the demo photos are royalty-free. Anything you add later — map SDKs, hosting, an API — is billed by whoever provides it, not by us.
Spec
measured| Screen widgets | 21 |
|---|---|
| Routes | 17 |
| Reusable widgets | 14 |
| Dart files | 89 |
| Data models | 8 |
| Mock services | 3 |
| Tests in the package | 8 |
| Dependencies | 3 (get, google_fonts, cupertino_icons) |
| Themes | Light + dark, one token file |
| Platforms | iOS + Android, one codebase |
Measured from nestora-v1.0.zip on 2026-08-30, not copied from the listing.
What you need
Flutter 3.29 or newer, Dart 3.7. Any machine that runs Flutter runs this: no backend to stand up, no keys to obtain, no Docker.
Questions
Is this the same package sold on CodeCanyon?
The same zip, the same version. You pay less here because there is no marketplace fee in the middle.
Can I use it in a client project?
Yes — one end product per licence, client work included. You cannot resell the source itself.
How much work is swapping in my own API?
Three service files hold every call, and each already returns a Future. Replace the bodies; the controllers and screens do not change.
Other kits
same architectureCheckout runs on Gumroad — PayPal and cards, invoice and VAT handled, download straight after.