// the take
A Flutter app and Express/TypeScript backend for the Hotter'n Hell Hundred cycling weekend in Wichita Falls, TX. It covers the event schedule, registration, local places, sponsors, and race-day route and tracking screens, backed by MongoDB. It suits anyone who wants a worked example of Clean Architecture in a real multi-screen Flutter app, or someone who rides the event and wants to see how the route data is put together.
- The Flutter side separates domain entities, repository interfaces, usecases, and data implementations, using the presenter/controller pattern from flutter_clean_architecture. Pages depend on usecases rather than HTTP code, so the data layer can change without touching the views.
- routeCreator.ts turns each distance's GPX file into a generated coordinate module (100_mile.gpxCoordinates.ts and so on). The course geometry is versioned with the code and served from the backend, not hand-typed into the client.
- The backend follows the same split: controllers and routes are separate, and each entity has its own interfaces folder with plain, Document, and Model types. A verifyToken middleware guards the authenticated routes.
- CircleCI is configured, and there are unit tests for the data repositories, domain entities, and the get_hhh and location tracking usecases.
- The last push was August 2020. Nothing in the listing shows the project still builds on a current Flutter or Node toolchain, so expect dependency upgrades before it runs.
- The README is the stock Flutter template plus a Trello link. It says nothing about running the Express backend, seeding MongoDB, or setting environment variables, so a newcomer has to read the code to find out how to start it.
- The test directory covers the Flutter data, domain, and usecase layers only. There are no widget or integration tests for the registration flow or the race-day map, and the backend has no tests at all.
- lib/data/utils/sensitive.dart sits in the client bundle, and its name suggests keys or secrets. Check it before anyone forks the repo or ships the app.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →