Thunkable submits the binary for you. Guideline 4.2.6 is the rule about exactly that: apps created from a commercialized template or app generation service are rejected unless they are submitted directly by the provider of the app’s content. A builder that submits on your behalf is carrying a risk that a builder handing you the keys is not.
Thunkable will publish to the App Store for you, which is convenient right up until it is the problem: a generation service submitting on a client’s behalf is the arrangement guideline 4.2.6 names directly. The sharper practical risk is reported continuity — apps are unpublished from the store when a subscription lapses, which makes your listing a function of your billing status.
2 claims, each one read off a document that says it.
Apps are reported to be unpublished from the store when a subscription ends.
A service submitting on a client’s behalf is the arrangement 4.2.6 rejects.
"Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content. These services should not submit apps on behalf of their clients and should offer tools that let their clients create customized, innovative apps that provide unique customer experiences."
One claim, read off a document that says it.
Thunkable publishes directly to the App Store.
One claim, read off a document that says it.
Paid tiers start at $18/month (yearly) or $19 (monthly), but a live published app first appears on the $37/$59 Builder tier.
"Accelerator $18 $19 /month … 20,000 AI tokens 5 Public Projects 1 Private Project 10 Screens Per Project … Builder $37 $59 /month … 1 Live Published App"