Learn
Every word this hub uses, in one place.
The footer on every page promises a definition for anything unfamiliar. This is where that promise is kept.
Glossary
Alphabetical, one line each, true of this portfolio rather than of software in general. A missing word here is worth reporting.
- AAC
Augmentative and Alternative Communication: help communicating without speech, like Floomp's big-text screen.
- Access
Cloudflare Access, the sign-in gate on this hub; only a signed pass from a saofal.com address gets through.
- Accessibility
How well an app works for someone with a disability; it is why Floomp's colour themes are free.
- App Store Connect
Apple's own web portal for managing an app: its listing, its price, its in-app purchases, and whether it is allowed to ship.
- ASO
App Store Optimization: getting an app found and chosen in a store's own search, covered for all seven apps in docs/ASO.md.
- Bug
A finding where the app does the wrong thing, as opposed to a gap (missing something) or a nit (a rough edge).
- Build
One compiled, installable version of an app; Ship it lists twelve steps from a finished build to someone downloading it.
- Certificate
Apple's proof that a build was made by this team; without one, an app cannot be signed for a real device or a store.
- Cloudflare Pages
Cloudflare's static-site host; this crew hub runs on it, alongside Cloudflare Access and the D1 database that stores the board.
- Competitor analysis
A mission that takes one real rival app apart, honestly, including what it does better than this portfolio.
- Conversion rate
The share of people who see a store listing and actually install it; docs/ASO.md treats it as a direct ranking signal on both stores.
- D1
Cloudflare's database; this hub's own board and submissions live in one, named slate-crew-hub.
- Encryption at rest
Data scrambled by a key while it sits stored on the phone, so a lost or stolen device still keeps its data locked.
- Free tier
What an app gives away with no payment at all, for example Inkby's four cards, before a subscription or unlock adds more.
- In-app purchase
A payment made inside the app, through Apple's or Google's own billing; every paywall here uses one.
- Keyword cluster
The small group of related search words a listing leans on; docs/ASO.md gives each app one, since all seven names are invented.
- KMP
Kotlin Multiplatform: the shared code, written once, that both the iPhone and Android versions of an app run for their non-visual logic.
- Lifetime purchase
A single payment that unlocks an app forever, nothing to renew; Decoyo, and the lifetime option on Inkby, Voff and Dwindy, all work this way.
- Listing
An app's page on the App Store or Google Play: its name, its screenshots, its description, and its price.
- Lock screen widget
A small live view on the iPhone's lock screen itself; it is where Inkby's handwritten card is seen every day without opening the app.
- Native app
Written in the phone's own toolkit, not a shared web view; SwiftUI on iPhone and Jetpack Compose on Android.
- OCR
Optical character recognition: the phone reading text out of a photo; Vault (Reepa) uses its phone's own OCR to read a receipt without uploading it.
- On-device
The app does its work on the phone itself and sends nothing to a server, which is why none of the seven apps has an account at all.
- One-time unlock
A single payment, no subscription, that removes an app's free-tier limits for good; how Duezy, Vault and Floomp are priced.
- Paywall
The screen that shows a price and what it unlocks; every one here states the price plainly and offers Restore.
- Play Console
Google's own web portal for managing an Android app: its listing, its price, its release tracks, and whether it is allowed to ship.
- Privacy policy
A hosted page explaining what an app does with data; both stores require one per app before submission, even for a free tier.
- Provisioning profile
Apple's file that authorizes a signed build for a release; a store profile ties it to the app, not a device, sitting alongside a certificate.
- Release track
A staged rollout lane a build passes through before reaching everyone at once, such as Play Console's internal, closed and open tracks.
- Review (store)
The rating and written comment a customer leaves on an app's own store listing, not a code review or one of this hub's own findings.
- Sandbox purchase
A real purchase made in Apple's or Google's test storefront, used to prove a paywall actually unlocks, survives a restart, and restores.
- Severity
How much a finding matters: blocks (could not finish), annoys (finished, but it cost you), or polish (worked, could be nicer).
- Signing
The cryptographic step that proves a build came from this team; it needs a certificate and profile on iOS, an upload key on Android.
- Simulator and emulator
A virtual iPhone (simulator) or virtual Android phone (emulator) run on a computer, used for testing everything except real hardware.
- Store screenshot
An image of the app captured for its store listing; the twelve-step pipeline on Ship it still needs a real device to take these.
- Subscription
A recurring payment, billed automatically until cancelled; Inkby, Voff and Dwindy each offer one alongside a lifetime option.
- Tester
Someone outside this team who tries a build early, through TestFlight or a Play Console release track, before the public release.
- TestFlight
Apple's own way to put a build in front of testers before it reaches the public App Store.
- Upload key
The private key an Android build is signed with before upload; Play App Signing then re-signs it with the real distribution key.
- Widget
A small live view pinned to a phone's home screen that recomputes itself fresh every time it draws, never from a saved number.
Resources
Outbound reading worth actually opening, plus the two repository documents behind the facts on this page.
- App Review Guidelines
-
The rules every one of these seven apps has to pass before Apple allows it to ship.
- App Store Connect help
-
Apple's App Store Connect help
How to actually create the app record, the builds and the in-app purchases, inside Apple's own console.
- Developer Policy Center
-
Google Play's Developer Policy Center
The Android equivalent of Apple's guidelines: what Google Play allows, and what gets an app rejected.
- Data Safety form guidance
-
Google's Data Safety form guidance
How to fill in the form that, for every one of these apps, should read as no data collected.
- Human Interface Guidelines
-
Apple's Human Interface Guidelines
Apple's own design rules for iOS, the ones every SwiftUI screen in this portfolio is built against.
- Material Design
-
Google's design system for Android, the equivalent reference for every Jetpack Compose screen here.
- docs/ASO.md
-
docs/ASO.md, in this repository
The store-search kit: the exact name, subtitle and keyword cluster planned for each of the seven apps.
- docs/PRICING.md
-
docs/PRICING.md, in this repository
The pricing sheet: what each app actually charges, and why, market by market.
How to set up a project
Five stages, in order: a goal, the scope, the milestones, the tasks, and a plain test for done.
Goal
What finished actually looks like, in one sentence.
Scope
What is deliberately left out, and why.
Milestones
Checkpoints on the way to done.
Tasks
The concrete steps inside each milestone.
Done
A plain, testable line that says the project is finished.
This portfolio, run through the five stages
- Goal
Seven apps live on the App Store and Google Play at once, each with its own listing.
- Scope
Excludes anything that needs a server. This crew hub is the one exception, and it stays separate from the seven apps it is about.
- Milestones
Build, then harden, then submit. Build and harden are both done; submit is the one waiting on the owner.
- Tasks
The twelve pipeline steps on Ship it, from building the app on both platforms to shipping it to TestFlight and the Play internal track.
- Done
Someone outside this crew can find one of the seven apps in a store and download it.