DayBloom — planner, money & journal app

DayBloom: a complete Expo / React Native app, ready to rebrand

DayBloom is a complete, offline-first life-tracking app built with Expo and TypeScript. It ships as full source code: 229 files, with no backend to set up. Rebrand it, change the bundle ID, and publish.

What's inside the app

• Habits: daily, weekday and custom schedules, streaks, best streak, completion rates, archive and restore.

• Planner: dated tasks and priorities with a lightweight agenda view.

• Money: budgets, income and expenses, per-category totals, currency support.

• Journal: entries with mood and tags, search, edit, and delete with undo.

• Wellness: mood check-ins and wellness logs.

• Insights: trends computed from the user's own data.

• Mindful: a calm breathing and reflection screen.

• Settings: light/dark theme, reminders, JSON backup export/import, reset-all-data, privacy and support links.

• Onboarding: a first-run flow with a tested fresh-profile path.

Tech stack

• Expo SDK 58, React Native, TypeScript (strict), Expo Router

• AsyncStorage persistence, expo-notifications for the optional daily reminder, expo-image for bundled artwork

• 26 pure-logic checks and 24 Playwright end-to-end tests, all passing

• expo-doctor: 20/20 checks passing

• No backend, no accounts, no analytics, no ads, no API keys. Nothing is downloaded at runtime; every screen, font and image is bundled.

What you receive

• Full source (229 files): app/ screens, src/ components and features, tests, docs, assets

• 12 documents: setup, architecture, rebranding checklist, store-publishing checklist, privacy-policy template, third-party licence notices, changelog

• 22 store-sized screenshots: 11 iOS at 1290×2796 and 11 Android at 1080×2400

• A signed Android preview APK (package com.daybloom.app, version 1.0.0) for demo purposes

Before you publish

1. Change com.daybloom.app in app.json (iOS bundle ID and Android package) to an identifier you own.

2. Run eas init to create your own Expo project ID. None is included.

3. Rebuild with eas build and re-test on a device. The included APK is signed with the seller's key, and the keystore is not included.

4. Replace the two legal URLs in src/config/brand.ts and host your own privacy policy.

5. Review the Money and Wellness screens and add any disclaimers your target stores or regions require (the app is not medical or financial advice).

6. Have the included LICENSE template reviewed before you rely on it.

Honest limitations

• This is unreleased source code: no users, no revenue, no store listings and no brand equity included.

• The Android APK was installed and tested on a physical Android device. The app has not been tested on a physical iPhone.

• Screenshots were rendered from the web export at store pixel sizes. Re-capture them natively if a store rejects them.

• Notifications may behave differently in Expo Go than in a development or EAS build. Use a development build to test reminders.

• LICENSE is a template, not legal advice.

• npm audit reports 4 high advisories in Expo build tooling. Do not run npm audit fix --force, because it downgrades Expo SDK 58 to 54 and breaks the app.

• Support: [state what you offer, e.g. "bug-fix updates for 30 days via the marketplace comments" or "no support included"].

Who it's for

Developers and studios who want a tested, well-structured Expo codebase to rebrand instead of starting from an empty create-expo-app.