Ship a planner that answers the one question a to-do list cannot: does today actually fit. 28 finished screens, every task carrying a time estimate, a day drawn as a wall of bricks against the hours you really have, and a fourteen day horizon you fix by dragging one brick. Light and dark themes, GetX architecture, offline documentation, an encrypted Laravel cloud backup, and a one-page product website ready to publish.

Demo Instructions: three intro screens open the app, then the sign-in screen is a mock that contacts no server and accepts any credentials. Use [email protected] / demo1234, or tap Sign in with both fields empty. There is nothing to register and no key to enter: a worked fortnight of 28 tasks across 3 projects is already loaded, and today in it is deliberately over its line, so the screen that makes the argument is the first one the preview opens on.

Why this one

• Height is the argument: a brick is as tall as its estimate, so an overloaded day is visibly a wall that will not fit and nobody reads a percentage.
• Ready to show on day one: 28 screens and a worked fortnight already written, with two days deliberately over capacity. Nothing looks half-built.
• Your brand in an afternoon: every color, radius and type token lives in one file. Change the primary hex; the launcher icon and the landing page follow.
• Tested, not just screenshotted: 115 Flutter tests pass, plus 27 on the back end, and the driver walks 56 frames in both themes.

The screens people will remember

• The wall: today’s tasks stacked as bricks against a dashed string line set to that weekday’s hours; anything standing above it is hatched before the day starts.
• The horizon: fourteen days, each its own small wall at the same scale with its own line. Drag a brick from a heavy day onto a light one and both recompute where you dropped it.
• The heft factor: recorded time divided by what you estimated, printed as a multiplier, with the corrected figure shown beside every new estimate and never written over it.

Plus the screens a real app needs: an inbox with search and project filters, a task view with subtasks, a timer, typed-in minutes and dependencies that refuse to close a loop, working hours per weekday and per single day, projects with their own edge color, labels, standing tasks that clamp to the end of a short month, a waiting-on view, a finished log, cloud backup, settings, and an onboarding flow.

Laravel back end included

The download ships a Laravel application with a Filament admin panel (backend/): it stores an encrypted backup snapshot per user behind Sanctum tokens, keeps five versions with the oldest pruned, and lets an operator see who is using the space without ever reading the contents. The app runs perfectly well without it — every task lives in the phone’s encrypted store and the app makes no network request until a server address is typed into Cloud backup. Deployment needs PHP 8.4 or the included Docker Compose file; hosting is yours.

Landing page included

The download ships a one-page product website for your app (landing/): hero with two phone mock-ups, three feature tiles, a swipeable screen gallery, FAQ and store buttons, already set in the same colors and typefaces as the app and filled with its real screenshots. It is a single self-contained HTML file with no frameworks and no external requests, so you can put it on any static host in a minute and replace the copy and store links from the marked spots.

Built for developers

• Clean GetX architecture: View, Controller, Service, Model, with lazy bindings per route.
• A pure Dart engine you can lift out: the wall layout, the horizon, deferral, the heft factor, the weekly review and the dependency graph live in data/engine/load_engine.dart with no Flutter import and the clock injected as a parameter.
• Swap in your API without touching a screen: the worked fortnight sits in one file behind a single service; six schema-versioned stores are the only thing that writes.
• Five Dart dependencies: get, http, share_plus, flutter_secure_storage and cupertino_icons. Two typefaces ship as four static files, so nothing is fetched at first launch.
• Theme-aware components: the same widgets look right in light and dark, and the brand color is defined in three grades so a button label and a store thumbnail can both be right.

What you get: full Flutter source code, README with re-theming and API integration guide, offline HTML documentation (34 chapters, 13 screenshots and 2 interaction GIFs), the sample data layer, light and dark themes, the landing page, and the companion back end with its own deployment guide.

Notes

The sign-in and registration screens are interface only and perform no authentication; the app’s records are not protected by them. Local notifications, calendar sync and multi-person sharing are not wired in this version. Figma or Sketch source files are not included; the interface is defined in the Dart source.

All in-app imagery is drawn on canvas or set in type. No third-party photographs are bundled or required, and the two typefaces are included as files under the SIL Open Font License 1.1.

Third-party services and external costs: Heftora runs on bundled sample data out of the box and makes no network request. Connecting it to live services such as Firebase, REST APIs or payment gateways will involve those third-party services, which will incur their own separate costs and are not part of this item. The back end needs PHP 8.4 or Docker and a host of your own.