Daily history and score trends with fictional sample records.
Optional supporter badge after a RevenueCat Test Store purchase. Core features stay free.
CorkWill Log app icon (1024 x 1024).

Inspiration

I built CorkWill Log because I wanted a quick way to look back on my day. A generic habit streak did not capture what made a day feel meaningful. I wanted a few questions, a score I could understand, and a history that would help me spot patterns over time.

What it does

CorkWill Log lets you answer a few of daily questions and see how your score changes. You can edit the questions, point values, and evaluation labels to match your priorities. It saves answers as you go, shows trends and past records, supports English and Japanese, and lets you export your data. Daily logging, history, customization, and exports remain free.

How I built it

CorkWill Log started as a web app using TypeScript, React, vinext, Cloudflare Workers, and D1. For Shipaton, I added a Capacitor iOS review build and integrated the RevenueCat Capacitor SDK with RevenueCat Test Store. An optional one-time test purchase can activate a supporter badge, but only after the app checks the expected active RevenueCat entitlement. Cancellation, failure, and restoration are handled explicitly. No real money, card details, or recurring subscription are involved in this submission build.

I also made a local review setup with fictional records and an isolated database. Reviewers can run the native iOS experience in the Simulator from the public source repository without a paid Apple developer account. The web app existed before Shipaton; the iOS target, RevenueCat integration, purchase tests, and review setup were added for this entry.

Challenges and what I learned

Bringing a native purchase flow into an existing web app meant accounting for asynchronous SDK operations, account changes, failed purchases, and restore behavior. I learned to use RevenueCat's actual entitlement state as the source of truth rather than granting a badge with a local flag. I also learned how to make a test purchase flow reproducible for reviewers without touching production accounts or payments.

What's next

I want to learn whether optional support is useful without restricting access to personal records, improve the native experience, and consider store distribution after the prototype. AI tools assisted with coding and research; I made the decisions about what was built.

Review setup: https://github.com/ryoyamag51/corkwill_log/blob/codex/shipaton-next-gen/docs/shipaton/REVIEW.md