Welcome #

Welcome to NativeWebApps!

The best way to get acquainted with NativeWebApps is to head over to,  build a sample app.

Additional configuration options further enhance the native Android & iOS mobile apps that NativeWebApps will generate for you.

Some of the available configuration options are explained below, but sometimes the best approach is simple trial and error to see how things work in your app. Please email us if we can answer any further questions.

Yes No
App Styling #
App Icon #

Upload a square image to use as your app’s icon. Recommended resolution is 512×512 pixels.

If your image has transparency, it will be given a white background. For Android, a small rounding of the corners of your image will be applied. This same effect is automatically applied to your app icon on iOS by the operating system.

Yes No
Custom CSS #

You may enter any custom CSS that you would like applied to each page in your app.

One of the most common usages is to hide/ remove your web navigation elements when using native sidebar navigation. You can also hide any part of website which you don’t wanna add in apps, such as the header and footer.

You can send us class name or id.

Yes No
Push Notifications #

Push Notifications are an incredibly powerful feature. When selected, we integrate OneSignal’s Push SDK into your app to support the full range of what you might want to do with push notifications.

OneSignal offers a feature-rich, enterprise-class push notification service completely free of charge (they make their money through enterprise support and customizations). Learn more at

  • Send push notifications to individual devices, groups of devices, or all devices at once
  • Send via the dashboard, or programmatically through their API
  • Optionally specify a target URL to open within your app when the notification is clicked
Yes No
Build Settings #
iOS Bundle Id #

The Bundle Id is never visible to end users. However, it is required to match the provisioning profiles and certificates you set up in your Apple developer account prior to publishing. It is not possible to change your app’s Package Name once your app is published.

Apple recommends the Bundle Id follow reverse domain name service notation. For example, if your website is, your Bundle Id might be

Yes No
Android Package Name #

Unlike the iOS Bundle Id, your app’s Android Package Name is visible to users in your app’s Google Play Store URL. It is not possible to change your app’s Package Name once your app is published.

Google recommends the Package Name follow reverse domain name service notation. For example, if your website is, your Package Name might be

Note that dashes or spaces are not allowed. Also, it’s not permitted to start any section of the package name with a number.

Yes No
App Store Publishing #

f you are a developer, you may simply download the complete source code for your app and publish using standard methods.

NativeWebApps offers various configuration, consulting and publishing services. Please email us if you may be interested.

Yes No
Apple App Store #
Apple Developer Account

You must have a valid Apple Developer Account in order to publish your app to the Apple App Store.

Learn more at

One registered, you’ll need to generate your signing certificates. Learn more at Maintaining Your Signing Identities and Certificates.

iTunesConnect App Store Listing

Create your app store listing at You’ll need to fill out several pieces of information including app name, description, search keywords, screenshots for the various devices sizes, content rating, contact person and a few more.

You will see a place to select the build you want to submit to the App Store. Most likely, there won’t yet be a build you are able to select, as you have not yet uploaded one. Please see the next step below.

Uploading Your Build

You may download the complete iOS source code for your app from you GoNative app’s manage page. Uncompress the ios_source.tar.gz file (you might use tar -xzvf ios_source.tar.gz using Terminal on Mac OSX). Then, open GoNativeIOS.xcodeproj in Xcode.

You’ll want to be sure that your developer account is added to Xcode, and that the Provisioning Profile you generated previously is available to use. You may double check that your app’s Bundle Id is set correctly in your app’s General settings.

You can now go to Product -> Archive in the menus. If Archive is grayed out, make sure to select Generic iOS Device in the top left of the Xcode window. Once your app is Archived, you’ll see a button to upload the build to the App Store. After the upload is successful, it sometimes takes an hour before the build appears in your iTunesConnect app store listing.

Once your build is selected, and all your App Store listing data is filled out, you may click the “Submit for Review” button in the top right. On the next page, you may be asked questions about Cryptography, the Advertising Identifier, and 3rd Party Content. GoNative apps do NOT use Cryptography, and do NOT use the Advertising Identifier. You will have to determine for yourself if your app uses 3rd party content, and if you have the rights to it.

Yes No
Android Google Play #
Google Developer Account

You must have a valid Google Developer Account in order to publish your app to Google Play.

Learn more at

Submitting Your Build

You may take the Android APK file generated by GoNative and available on your GoNative app’s manage page, and upload it directly to Google as part of your app store submission. You may also download the complete Android source code and generate the APK yourself.

Similar to Apple, you will have to fill out an assortment of data regarding your app store listing, including app name, description, screenshots, several image assets, a content rating, and more.

Once submitted, your Android app should be live in Google Play app store within a few hours.

Yes No