Questions, answered plainly
Packages, platforms, stores, timelines, and money. The answers here are the same ones you would get in a first reply, so nothing changes after you pay.
The packages
Is the cheapest package just a web view?
Yes, and we say so rather than dress it up. At the entry price the app is a tuned native shell around a site you already run, with your icon, splash, and navigation. If a store needs more unique functionality than that, we scope native screens as a custom build instead of selling you a wrapper that may not pass review.
What is actually included in the website package?
The app build for Android, iOS, or both, the app name, launcher icon, splash setup, basic navigation and back-button behaviour, a signed build you can distribute, and one round of revisions. Hosting, domain, content, and new native features are not included.
Does BeeBuild touch my website?
No. The package wraps what is already live. Changes to the site itself are your team's work unless a separate scope says otherwise.
Can the app work offline?
The shell handles temporary connection loss and retries, but real offline data entry is a custom feature, not part of the entry package.
Platforms and stores
Do you build iOS as well as Android?
Yes. The website package prices Android, iOS, or both separately, and custom categories cover both platforms at one starting price unless the category lists platform prices.
Do you guarantee Google Play or App Store approval?
No, and nobody honestly can. We prepare builds against the published requirements, flag thin-wrapper risk before you pay, and hand over a submission checklist. The decision belongs to the stores.
Who owns the developer accounts?
You do. Android and Apple developer accounts stay in your name, which is why store fees are paid by you directly to the stores.
Is closed testing included?
No. Closed testing is handled by TesterBee as a separate service with its own pricing. It links from here but is never bundled into a BeeBuild package.
Working together
How long does a build take?
The website package typically runs one to two weeks. Custom categories range from roughly four weeks for a business utility to twelve or more for a marketplace. Each category lists its typical window, and the quote confirms yours.
Who does the work?
AI-assisted tooling produces the first draft of screens, models, and tests. A developer reviews every line, owns architecture and security decisions, and ships the release. No project is generated and left unreviewed.
How are revisions handled?
The package includes one round inside the agreed scope. Additional rounds and new features are quoted before they are built, so the invoice never grows quietly.
Can you integrate with the systems we already run?
Usually. Payments, CRM, ERP, booking engines, and in-house APIs are common. If a system has no usable API, we will say that early rather than discovering it in week six.
Do you maintain the app afterwards?
Maintenance is a separate arrangement, scoped monthly or per change. It is never assumed to be included in a build.
How do payments work?
Nothing is charged from the request form. After the scope and price are confirmed, card payment runs through Stripe when it is enabled for the project, or we invoice. Store fees stay separate.
Still unsure which package fits?
Send the website or a short description. We will tell you which category fits, and say so if the answer is 'not yet'.