EdTech & Wellbeing
How Dazzl Got Ten Months of End-to-End Ownership on a Gamified Wellbeing App
Techparser has owned Dazzl end to end for 10+ months: a gamified student wellbeing app with 52 feature modules and five sign-in methods on Flutter and Firebase.
- Client
- Dazzl
- Industry
- EdTech & Wellbeing
- Timeline
- September 2025 – present
- Team
- 1 engineer with end-to-end ownership
Results
- 10+ months
- End-to-end ownership since September 2025
- 52
- Feature modules across 54 routes in the codebase
- 5
- Sign-in methods: email, Google, Apple, Kakao and Naver
The problem
Dazzl turns self-improvement into a game for students. Tasks, goals and wellbeing habits earn gems, pets and furniture for a virtual room, and guided audio sessions move the user through quests. That makes it several apps in one: a productivity tool with recurring tasks and analytics, an audio and video content platform with lock-screen playback, and a game with its own economy, badges and levels. All of it has to feel simple to a student holding a phone between classes.
The founder, Cheryl, needed a developer who could own that breadth end to end rather than execute tickets: think through the edge cases in repeating tasks and reward rules, propose solutions, and keep shipping as the product changed direction. The app also had to serve Korean as well as English users, including sign-in through Kakao and Naver, and it had to keep working for a student on a train or in an exam hall with no signal.
What Techparser built
- Tasks and goals with categories, priorities, daily, weekly and monthly repeat schedules, reminders, an analytics dashboard and reports on completion, patterns and mood against focus.
- Focus sessions with background music, and a Tools tab of wellbeing exercises: mood check-ins, breathing, guided audio resets, journaling and exam-anxiety tools.
- Audio and video content: superpower, spotlight and sleep sessions with lock-screen controls, an app-wide mini player and caching of played audio.
- Gamification: quests that pay gems and unlock pets, a fortress room with eleven furniture slots, eight identity levels, badges, victory logs and a reward wheel.
- Five sign-in options: email, Google, Apple, Kakao and Naver, the last two through Cloud Functions that mint Firebase custom tokens.
- Two locales, English and Korean, with a spreadsheet-driven translation pipeline, plus light and dark themes.
- Offline support: tasks and focus sessions work without a connection using Firestore's on-device cache, with a status strip and reminder catch-up on reconnect.
- PostHog analytics, Crashlytics crash reporting, OneSignal push, and custom Rive and Lottie animations throughout.
Decisions that mattered
Care where gamified apps break
Repeating tasks, date ranges and reward rules are where products like this usually go wrong, and they got the most attention. A recurring task is stored once as a template and expanded into daily instances, gems are awarded through a single table of activity types, and identity credits can be earned at most once per calendar day. The founder called out that Techparser 'thinks through edge cases and proposes solutions' rather than simply executing tasks.
One architecture across 52 modules
A product this broad needs the same shape everywhere or it becomes unmaintainable. Every feature follows a five-layer structure: view, controller, store, repository and model, with typed route arguments and a single error handler that times out, maps Firestore errors to translated messages and reports to Crashlytics. Fifty-two feature modules and fifty-four routes share that pattern, along with one design system of X-prefixed widgets and brightness-aware colours, so a new screen looks and behaves like the others by default.
Offline without a second database
Students use Dazzl in exam halls and on trains. Rather than add a local database and a sync engine, the offline work leans on Firestore's persisted write queue: task and focus writes complete locally first, a banner shows offline and syncing states, and reminders that could not be scheduled offline are caught up on reconnect. No new collection or field was needed, which kept the live data model stable while the feature shipped.
Clear, frequent updates
A product this broad changes direction often. Frequent, specific progress updates meant the founder always knew where things stood, and a change of direction could be made before code was built on an assumption that no longer held. Cheryl’s video review singles out communication and project management as a strength of the engagement alongside the code itself.
Outcome
Dazzl has been in continuous development since September 2025, with Techparser owning the app end to end for more than ten months as of September 2026. The codebase stands at version 1.9.8, with 52 feature modules, two languages and five sign-in methods, and it ships with light and dark themes and offline support for tasks and focus sessions.
The founder recorded a video testimonial describing the project as genuinely complex and recommending Techparser without hesitation to anyone looking for a developer who can take real ownership of a complex product.
“The project has been genuinely complex, involving task management with analytics, audio and video content delivery, a full gamification system, custom animations, and more features… And Zoraiz has owned this end to end. He doesn’t simply execute tasks. He thinks through edge cases and proposes solutions… I would recommend Zoraiz without hesitation to anyone looking for a developer who can take real ownership of a complex product.”
Questions about this project
- How long has Techparser worked on Dazzl?
- Since September 2025, which is more than ten months as of September 2026, with end-to-end ownership of the Flutter app throughout. The engagement is ongoing: the codebase is on version 1.9.8 and new features such as offline support and Korean social login were added during that period rather than at the start.
- What technology stack does Dazzl use?
- Flutter on Firebase: Firestore, Auth, Storage, Cloud Functions written in TypeScript, and Crashlytics. Analytics run through PostHog, push through OneSignal, audio through audioplayers and audio_service for lock-screen controls, and animations through Rive and Lottie. Kakao and Naver sign-in go through Cloud Functions that mint Firebase custom tokens.
- Can Techparser take ownership of a complex app we already have?
- Yes. Dazzl is the reference case: a founder with a broad, changing product and one Techparser engineer who owns architecture, features, releases and communication. If your app has outgrown ticket-by-ticket development and you want someone who proposes solutions rather than waits for specifications, book a call and walk us through the product.
