Dayunfold

Today screen, no device frame (1206x2622)
7:02 AM. Most mornings your phone decides the shape of your day.
The frame: three gratitudes, identity and action, SIM and MAD, set in four minutes
App icon, 1024x1024
Pro paywall via RevenueCat: the ritual is free forever, Pro is the Companion (EUR 4.99/mo or 29.99/yr)
Journey: streaks forgive a missed day per week of consistency; patterns only from your own data
Journey: streak with embers and energy history, no device frame

Inspiration

Usually your days shape is define within first few minutes after you wake and for most, it's picking up the phone which sets the baseline. For months I ran a four-step morning ritual in a paper notebook before touching my phone. It worked well enough that I wanted it on the device.

What it does

A five-minute guided morning ritual in four steps:

Thankful: three specific gratitudes. The app teaches by example with inline vague-to-concrete hints.
Identity: who you are acting as today, anchored by one concrete action you can check off later that evening.
Stillness: a few minutes of no input. Sit, count breaths, or drink your coffee being mindful.
SIM & MAD: one move that creates momentum or moves you towards your goal, one thing that actually restores you.

Evenings close the loop: did SIM and MAD happen, an energy rating, one line about the day. Journey shows streaks (a missed day is forgiven for every week of consistency) and patterns drawn only from your own data: energy against moon phase, weather and daylight, each gated behind honest sample thresholds.

How I built it

Using Expo based on React Native with TypeScript, an own Node backend on a Hetzner VPS via Coolify with Postgres, in-house anonymous-first auth, PostHog for a five-event activation funnel, Sentry for errors. CI runs typecheck, lint, jest and a release APK build on every push, with Maestro smoke flows on an emulator.

Challenges

Shipping solo on roughly ten hours a week around a day job and a toddler. The reason the app exists is the reason it was hard to build.

The iOS guidelines 4.3(b) rejection history - the very first app I built which is similar to this but rather different core ideology, was rejected and it was biggest slap in my face that determined wether I keep pushing or give up.

Keyboard handling and data-loss edges found in a full pre-submission QA pass. The report about every challenge lives in the repo. I fix what I find and log what broke so I can reflect on every decision make and improve moving forward.

What's next for Dayunfold

Success and kill numbers are written down in the repo: I have to have a clear path forward and understanding on when to move forward and stop poking a dead-end or the app goes to maintenance honestly.

The whole run, from fork to QA findings to funnel numbers including the ugly ones, is documented at @k13birch with worklogs in git. I post the numbers either way.

I'll try to run some marketing and work on distribution, this is currently my biggest stumbling block with this and any app I've made before. Distribution is the thoughtest part and hope to take any given advice on that from this journey at Shipaton.