Frequently Asked Questions
Quick answers to common questions about Code2Native.
Getting Started
How long does it take to build an app?
Android builds land in 2-5 minutes and you can watch the log stream live. Cloud iOS builds run on real Apple silicon and take longer — upload your Apple distribution certificate (.p12) on the Agency plan to get back a signed, store-ready .ipa, or receive an unsigned .ipa to re-sign yourself.
Do I need coding skills?
No. For website and store apps you enter a URL, a name, and an icon — the Gradle and Xcode side is ours.
What types of websites work best?
Any responsive site served over HTTPS — stores, blogs, dashboards, PWAs. If it looks right at phone width in the free preview, it will look right in the app.
Can I try before paying?
Yes — the free tier includes one build credit, no card required. The live phone preview is free and doesn't spend it.
Pricing & Credits
How do credits work?
One build credit covers an Android build; Windows builds use 2 credits and iOS builds 3 (they run on dedicated Apple-silicon hardware). Credits never expire. The exact cost shows before you press Build, and builds that fail refund automatically.
What happens if my build fails?
Every failed build refunds its credit automatically — you never pay for a build that didn't produce your app. The build logs show exactly what went wrong so you can fix it and rebuild.
Do credits expire?
Credits don't expire as long as your account is active. Subscription tiers renew monthly.
App Store Submission
Can I publish to Google Play Store?
Yes. Pick 'Store' distribution, set your Application ID, and you get an AAB ready for Play Console upload. We generate and manage a persistent per-project upload key for you — or upload your own keystore if you prefer.
Can I publish to Apple App Store?
Cloud iOS builds are live: we build on real Apple silicon. Upload your Apple distribution certificate (.p12) on the Agency plan and we return a signed, store-ready IPA; without it you get an unsigned IPA to re-sign yourself. Either way we never need your Apple ID or App Store Connect access. iOS Web Clips remain available as the zero-signing option.
Will my app get rejected?
WebView apps can be approved if they provide value beyond just wrapping a website. We recommend adding push notifications, offline support, or native features. Follow our compliance checklist.
Who owns the app?
You do. You own the certificates, the store listing, and the published app. We're just the build tool.
Security & Privacy
Can you see my website content?
We only access your website during the build process to embed it in the app. We don't store your website data or analytics.
Is my signing key secure?
Yes. Signing keys are encrypted at rest and only used during builds. They're never logged or exposed in build output.
Do you add tracking to my app?
No. We don't inject any analytics or tracking. The only third-party integrations are ones you configure (like OneSignal or AdMob).
Technical
What native features are available?
Camera, location, biometrics (Face ID/Fingerprint), QR scanner, push notifications, secure storage, clipboard, sharing, and more. See our Native Bridge API documentation.
Can I use my own source code?
Yes. Upload a ZIP or point us at a Git repo. Flutter, native Android (Gradle), and Capacitor build today; React Native, Ionic, and Expo are waitlisted.
What Android versions are supported?
Our apps support Android 7.0 (API 24) and above, covering 95%+ of active devices.
Does the app work offline?
Yes. We include offline detection and a fallback page. For PWAs, your service worker is preserved for full offline support.
Still Have Questions?
Check our detailed guides or reach out to support.