What a small team needs ready before submitting an app to the stores, in order: before the first build, the test track, the store build, the listing, legal URLs, review rules and notes for the reviewer.
Read articleHow we ship ChronoFlow with GitHub Actions: two workflows per platform, the same commit rebuilt for the store, build numbers without collisions, iOS with no Mac in the way, and what stays manual.
Read articleFree on Cloudflare R2 and Pro on Backblaze B2: what we compared at public list prices, why not Azure Blob, what it costs per 1,000 accounts, and what we gained and gave up by choosing two providers.
Read articleWhy CORS breaks the ChronoFlow Samsung and LG apps but never the Flutter app: Origin null, preflights before authentication, every custom header on the list, bucket CORS, and one Vue codebase for web and TVs.
Read articleHow ChronoFlow models playlists, schedules and screen groups, picks the winner with source weights and priority, keeps the loop as screen state, and delivers a change in a second or two.
Read articleHow ChronoFlow keeps Free files in Cloudflare R2 and Pro files in Backblaze B2: one disk per plan, each file remembers its own, quotas checked twice, and a move that deletes the source last.
Read articleHow ChronoFlow serves the dashboard, the app and TVs with one Passport server: one client per channel, secrets only on the server, 1-day and 30-day sessions, and Google and Microsoft sign-in without blindly merging accounts.
Read articleHow a ChronoFlow screen joins an account: a six-character code that rotates every two minutes, a device secret, a claim inside one transaction, and a credential delivered exactly once.
Read articleHow a single ChronoFlow build is a console on a phone and a screen on a TV: a mode stored on the device, one shell per mode, Android TV detection, and a separate web Player for Samsung and LG.
Read article
