Build your own Habitica.

# Build an original app inspired by Habitica

You are an experienced mobile product designer and mobile engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: iOS / Android. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original native gamified task organizer called Questday, inspired by Habitica. It is for individuals who enjoy a light role-playing reward loop while tracking real tasks. The main journey is creating a habit or daily task, completing it, earning a documented reward, and spending earned points on original cosmetic items or a custom personal reward. Deliver native iOS/Android projects with a real task ledger, not an RPG dashboard with arbitrary counters.

## Design
Use an original friendly character style, clear sections for habits/dailies/to-dos, and readable reward feedback. Keep task completion fast and show the reason for every point change. Avoid copying pixel art, characters, monsters, or item names. Support screen readers, large touch targets, reduced motion, and neutral recovery messaging when a day is missed.

## Features
1. Task types: create repeatable habits, weekday-scheduled dailies, and one-time to-dos with title, note, and difficulty. Separate repeated habit events from daily completions and archive tasks while retaining history. Validate schedules and prevent accidental empty tasks.

2. Reward rules: apply a small documented experience/coin formula to confirmed completion events. Derive level from accumulated experience, prevent repeat rewards for the same daily/to-do completion, and show a readable activity log instead of mutable unexplained balances.

3. Original avatar: select a few original base appearances and unlock cosmetic items using earned coins. Preview before spending, prevent insufficient-balance purchases, and persist equipped items. No purchased currency or copied asset pack is necessary.

4. Personal rewards: define a reward such as a planned break with a coin cost, redeem it, and record the redemption. Undo the latest completion or redemption using a compensating event; do not duplicate rewards through repeated taps or app relaunch.

5. Daily routine: show today’s scheduled tasks and a local-calendar history, process a new day idempotently, and offer opt-in reminders. Allow offline creation/completion and a native share-sheet backup; notification denial must not block tasks.

## Tech stack
Use Flutter/Dart with both native project targets, SQLite, and a maintained local-notification adapter. Keep the task/event ledger and progression formulas in testable Dart domain modules, with a repository abstraction for persistence. Bundle original SVG or raster assets under clear licenses. A compatible existing native project can be retained, but a WebView or PWA cannot replace the requested app. The single-player edition needs no server, Habitica API, accounts, or in-app purchases.

## Data & behavior
Task {id, type, title, difficulty, schedule, archivedAt}; CompletionEvent {id, taskId, occurrenceKey, completedAt, rewardSnapshot}; LedgerEntry {id, causeId, currency, delta, reversesId}; Avatar; CosmeticItem; InventoryItem; PersonalReward; Redemption; DayCheckpoint; ReminderSetting. Apply events and rewards in one database transaction, constrain occurrence IDs, and derive balances from the ledger. Version rules so later formula changes do not rewrite old rewards. Preserve user-created content through import/export and schema migrations.

Acceptance checks and scope:
Complete a daily twice and verify one reward, complete a repeatable habit twice intentionally, undo an event, buy/equip an item, and redeem a custom reward offline. Test insufficient coins, midnight/day processing after relaunch, duplicate taps, interrupted transactions, denied reminders, and backup restore. Build native targets and exercise iOS/Android accessibility. Exclude copied Habitica assets, parties, multiplayer quests, punitive health loss, social chat, purchased currency, and cloud synchronization.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.