Launch β’ BillBeam
BillBeam Current Launch Checklist
This checklist reflects where BillBeam actually is right now: most of the visual work is done, the plans and subscriptions have been updated, payments are aligned, and the focus has shifted to TestFlight, Apple review, and a strong public release.
v2.0
Goal
Submit and launch with confidence
Priority
TestFlight + Apple + payments
Focus
Stability, clarity, and approval
1. Product and presentation
The main visual and structural work that needed to be solid before moving fully into Apple/TestFlight work.
- βSidebar, navigation, and general layout corrected
- βPricing, settings, public invoice, dashboard, changelog, and checklist updated
- βAutism awareness ribbon integrated
- βMobile view and overall visual polish reviewed
- βFinal major visual issues already corrected
2. Plans and subscriptions
The new product and pricing structure needs to stay consistent across the app, Stripe, and Apple.
- βNew Simple plan added to the app
- βPricing updated to reflect the new structure
- βStripe updated with the new prices/subscriptions
- βApple IAP keys added into Render
- β¬Verify in testing that the app uses the exact correct Apple products
3. Payments and real testing
This is the most important stage before uploading the next build: confirming that nothing essential broke.
- β¬Create a new account and test clean register/login flow
- β¬Test web Stripe upgrade flow end to end
- β¬Test Apple purchase flow inside the wrapper/iPhone app
- β¬Verify the correct plan appears on the account after purchase
- β¬Confirm upgrade buttons no longer show network errors or broken routes
4. Core flow checklist
Before final TestFlight submission, BillBeam should feel stable in its most important user flows.
- β¬Create invoice
- β¬Preview invoice
- β¬Save invoice
- β¬Download PDF
- β¬Send by email
- β¬Open public invoice
- β¬Add manual payment
- β¬Review settings, branding, and security
5. Xcode, build, and TestFlight
Once local and live checks look good, this is the natural next stage.
- β¬Increase version and build number in Xcode
- β¬Create new archive
- β¬Upload the new build to App Store Connect
- β¬Wait for TestFlight processing
- β¬Test the real build on iPhone before submitting for review
6. App Store and review
What needs to be buttoned up to reduce confusion during review and improve the chance of a clean approval.
- β¬Confirm the active subscriptions in App Store Connect are the correct ones
- β¬Add any required subscription screenshot if Apple requires it
- β¬Review description, pricing language, and final metadata
- β¬Submit the updated build for review
- β¬Have a simple explanation ready in case Apple asks about plans or payments
7. Legal, trust, and support
The app now looks serious. This layer needs to support that image publicly.
- βLegal pages already present in the app
- βFooter and legal links visible
- β¬Do a final review of legal and subscription copy
- β¬Confirm support/legal inboxes are active
- β¬Have a response ready for early users or review questions
8. After approval
What comes next once BillBeam is approved and publicly live.
- β¬Verify real or final sandbox purchase behavior in production
- β¬Monitor error logs and early user reports
- β¬Collect feedback on the Simple plan versus higher plans
- β¬Define the next major update carefully
Current priority
The priority now is to run through the real flows in the updated app, confirm that purchases and plans behave correctly, then upload a fresh Xcode build, move it through TestFlight, and submit that clean version to Apple.