Common questions

Practical answers for rollout, updates and access

These answers match the current phase: website + waitlist + Android release channel.

Why not upload the 300MB APK directly to Vercel static deploy?

You can in Vercel Pro, but a dedicated artifact path is cleaner. This setup keeps manifest and download flow separated.

How does the app know that a new version exists?

App startup reads /release/android/stable.json and compares local buildNumber against latest and minSupported.

Can non-paying users keep using the app forever?

Not in the planned target architecture. After GO, entitlement checks plus grace window control access.

Why launch waitlist before payment?

It avoids legal and operational risk while backend billing and entitlement logic are finalized.

Will iOS bypass App Store in this phase?

No. This implementation focuses on Android distribution first.