Ship it

Twelve steps from a finished app to a phone that has it.

Three of the twelve are done. The fourth is where the portfolio is waiting, and eight more sit downstream of it.

Step 1

Build the app on both platforms

Done. Every app runs its full feature set on iOS and Android: capture, add and edit, search, settings, paywall, onboarding, light and dark.

Step 2

Test it: 536 shared tests across 71 suites, plus a manual pass per app

Done. The shared test suite passes in full, and the functional pass on simulator and emulator is complete for every app.

Step 3

Encrypt, declare privacy, minimise permissions

Done. Storage is encrypted at rest, every iOS app carries its privacy manifest, and each app asks for only the permissions it uses.

Step 4

Open the developer accounts, Apple and Google

Waiting on the owner. This is the first step no amount of code can finish; it needs identity and legal verification only the owner can give.

Step 5

Create the signing material: certificates, profiles, upload key

Waiting. Sits behind step 4; the accounts have to exist before anything can be signed under them.

Step 6

Create the paid products in both consoles, with the exact IDs the apps already use

Waiting. The IDs and prices the apps expect are already fixed in code; they only need to be registered in the consoles.

Step 7

Make a real sandbox purchase and confirm it unlocks, survives a relaunch and restores

Waiting. The billing code is written and unit-tested; this is the one path that can only be proven against a real store.

Step 8

Host a privacy policy for each app

Waiting. Both stores require a hosted policy, even for a free tier, on a host that adds no tracking of its own.

Step 9

Fill the store privacy declarations: Data Not Collected, and Google's Data Safety form

Waiting. Both forms should read as no data collected, since none of the seven apps sends anything off the device.

Step 10

Write the listings and capture the screenshots per device size

Partly done. Listing copy already exists in fastlane/metadata/ for every app; the screenshots still need a real device to capture.

Step 11

Run it on a real phone, including widgets and reminders after a reboot

Waiting. Nothing here fails on a simulator or emulator; it is untested only because it needs hardware this machine does not have.

Step 12

Ship to TestFlight and the Play internal track, then release

Waiting. The last step, and the only one that makes any of this public.