Public Readiness Infrastructure

Shipped

• Completed the account creation and verification loop so a new user can create an account, confirm ownership, and land in the app without getting stuck between states.
• Tightened the Free-to-Pro path with clearer trial eligibility, plan status, checkout return handling, and subscription management copy.
• Made cancellation behavior safer and easier to understand: access continues through the active period, and the app explains what changes next.
• Cleaned up account and sync labels so settings show a simple user-facing state rather than setup language.
• Improved sign-out and checkout feedback, including visible progress while a checkout is running and a safer fallback when account-linked checkout cannot complete.
• Made subscription management account-backed, so a signed-in user can manage the plan from the account they already control.

Why

This release is less about a new screen and more about making the product safe to use outside my own test loop.

Account creation, plan activation, sync, cancellation, and sign-out all cross boundaries where confusing states can erode trust. What should happen when someone creates an account, starts a trial, then comes back to the app on the same device? The answer needs to be obvious inside the product, not reconstructed from support copy.

The goal for this pass was predictability. An account should either be created or clearly not created. A plan should reflect the real access state. Local training data should not be silently discarded just because someone is checking out, signing out, or managing a subscription.

Notes

• The subscription infrastructure is now in place for the current public beta scope.
• Trial eligibility is intentionally separate from account creation. If a device is not eligible for another trial, the account still works and the paid upgrade path remains available.
• Subscription management and cancellation are account-backed rather than device-only.

Next

• Monitor the first public beta usage for unclear copy, failed handoffs, and support signals.
• Keep tightening onboarding and first-run experience now that the account loop is in place.
• Continue avoiding internal implementation detail in public updates unless it directly helps users understand the product.