How To Run Mobi Ready

Transcription

1 How To Run Mobi Ready

2 White Label Editor First of all, your clients need to have a domain name. If they do not have one yet, they can purchase one, for example at ovh.com. A.com name costs some 5 / year. They are not required to purchase hosting service with their domain name. Then, they must have access to the DNS zones from the domain name management interface. DNS means Domain Name System. Don t worry, this is not too technical. They will usually find the DNS zones in the Domain section of their domain admin panel. When they find that section, they have to create a type CNAME or CNAME record. In this record they will have to enter the following info: domain name: their subdomain address: the address or your editor (for example, apps.yourdomain.com, if your platform is installed on a subdomain, or yourdomain.com if your platform is installed on a main domain) Here is an example of how it could look like (it depends on the domain admin panel):

3 Your clients can either choose to use their domain name exclusively as a white-label interface, or choose a subdomain (this is an example of the format: subdomain.mydomain.com). They have to enter the name of their domain or subdomain. If they have the option, they should set the TTL to the minimum value. If they don t have this option,they should not worry. It just helps their modifications to be taken into account more quickly. To finish, they must connect to their account on your platform. Then they have to enter their domain name. If they are using the domain for their white label admin panel, they must enter their domain name; if they are using a subdomain, they have to enter that name. If the CNAME has not been configured correctly, they will receive an error message.

4 White Label Editor Editor Settings Then they must not forget to customize their admin panel by clicking on this icon Screenon the left of their dashboard. They should note also that the customizations you make with this process will only appear in their white label editor, and not in their dashboard. If they were able to set the TTL to the minimum value, they should be able to access their white-label interface immediately by typing the name of their domain or subdomain into their web browser. If not, they should be able to access it within 24h.

5 Then, once they have built the application of their first client, they should create and access to the application for him and give him the link to their white label panel. Thanks to this his client will be able to manage his app on your client s admin without knowing he is using your platform. SERVER SETTINGS If, when creating a CNAME, you are redirected to another page than your Siberian, that means you have to change some settings in your server configuration. This happens because your platform is not the default website of your server or of your webspace. For Plesk panel users: If you see the default page of Parallel Plesk when entering the CNAME in your browser, do the following: connect to your plesk panel click on the Server tab in Tools & Resources click on IP Adresses click the IP of your server (the IPV4 one, not the IPV6 if you have IPV6) for Default site choose your platform, and save enter the CNAME in your browser and that should be ok. If you don t have Plesk panel (note that the process below will require you have a dedicated server or a VPS, with root access): You have to change the vhost configuration file on your server. You have to do the following: connect in SSH to your server

6 find the httpd.conf file of apache (if you have cpanel installed, most of the time this file is in /usr/local/apache/conf/) edit this file go down in the file to find the first entry which matches the webspace in which your platform is installed as well as other websites. For instance you can have your platform and other websites installed in /home/www/mywebspace/, with your platform installed in /home/www/mywebspace/platform (these are exemples) The first entry which matches your webspace should be another website (actually it should be the one on which you are landing when entering your CNAME in your browser). This entry begins by <VirtualHost xx.xx.xx.xx:80> where xx.xx.xx.xx is the IP of your server, and it ends with </VirtualHost>. Below <VirtualHost xx.xx.xx.xx:80> you will see the ServerName which match the address of your default website. Go down and now find the entry related to your platform. It also begins with <VirtualHost xx.xx.xx.xx:80> but the ServerName is the address of your platform. Copy all this entry beginning by <VirtualHost xx.xx.xx.xx:80> and ending by </VirtualHost>, paste it in a text editor. Go back to your SSH console, and comment all the lines related to this entry (the entry for your platform) by adding a # before each line (<VirtualHost xx.xx.xx.xx:80> and </VirtualHost> included). Go up in the file to the first entry of your webspace, the one we have seen on point 5, above <VirtualHost xx.xx.xx.xx:80> of this entry paste the entry of your platform (the one you have pasted in a text editor). Save and exit Restart apache by entering service httpd restart or service apache restart, depending of your server, and it s done. If you don t know how to do it, contact us in a bug ticket and send us your ssh root access.

7 Editor This is the panel from where you modify your app. From the design to the features. Promote Here you can download a QR code that leads to the download of your app once it is published. ANALYTICS In this tab you can see how many times you app has been downloaded and also the number of fidelity points used by your users. USERS

8 Here you can manage users that have access to the application, add a new one, remove one, and set what they can do in the app (add pages or not for example). SETTINGS Domain: set the url for your mobile application. And don t modify it once the app has been published unless you want to republish the app. Facebook: here you can set the API key from facebook for this application only. This is useful if your client wants to have his own Facebook app. Previewing Apps Here are the links to download the previewer app coming with the Editions: For iphones: id ?mt=8 For Androids: How To Publish IOS App In this article we are going to see how to publish an app on itunes. We will give some tips and a step by step video. TO KNOW BEFORE PUBLISHING

9 XCODE AND MACOS To publish an ios app you need a Mac computer because you must use Xcode software. Actually you can do that without a Mac computer but you have to emulate your computer to install Mac OS and then install Xcode on Mac OS. Here is an article about that: TO BE ORGANIZED As an app maker you may publish apps under your own developer account and under your clients ones. You have to be a little bit organized to manage it well. Here are some tips on how to be organized: Create a main folder for all your ios publication, named it IOS Create a subfolder per developer account. If all your clients have their own developer account, one subfolder = one client, but if you are going to publish under your own developer account for some clients there will be a subfolder at your name and other subfolders in it for each client In the developer account s folder, create subfolders: one named certificates (in it you will store all the certificates for this account), and other subfolders for each app that will be published under this account (of course at start there will not be any app subfolders until you get your first app to publish) In this app subfolder, create 2 subfolders: one named certificates (in it you will store all the certificates for this app), and another named screenshots (in it you will store all the screenshots for this app) The tree could be like that: IOS apps John Doe certificates John Doe 1st app certificates screenshots John Doe 2nd app certificates screenshots Mary Sullivan certificates

10 Mary Sullivan 1st app certificates screenshots Mary Sullivan 2nd app certificates screenshots Mary Sullivan 3rd app certificates screenshots My Own Account (your account with which you publish apps for the clients that have not a developer account) certificates Patrick Johnson Patrick Johnson 1st app certificates screenshots Patrick Johnson 2nd app certificatesn screenshots Mike Morten Mike Morten 1st app certificates screenshots Certificates An ios publication under one developer account needs 4 files, one file that will sign the certificates and 3 certificates. The file that will sign the certificates and one of the 3 certificates are used for all apps published under this developer account, and the two other certificates must be created each time you will publish a new app. The ones that are used for all apps published under one developer account: These 2 files will be created once (the first time you are going to publish under this developer account). It is the Certificate Signing Request (CSR) and the ios distribution certificate (ios_distribution). The CSR is created from your computer (must be a Mac) from the keychain access, and the ios_distribution is created from the Member Center at developer.apple.com. These two items must be stored in the main certificates folfer for this developer account. Thus if we consider the previous example, for the client named John Doe who has his own developer account: IOS apps

11 John Doe certificates > CSR and ios_distribution for John Doe account must be stored here after you have created them John Doe 1st app certificates screenshots You will use this CSR and ios_distribution certificate for all the apps that you will publish for John Doe, if he buys several apps. You create once and you use them each time you publish an app for John Doe under his account. For your information, the Keychain Access to create the CSR is in your Mac in Applications > Utilities. The two other certificates are the aps_production certificate and the Mobile Provisionning Profile. You will have to create them for each app as you can see in the video. You will stored them in the certificates folder which is in the app folder. Thus if we consider the previous example, for the client named John Doe who has his own developer account: IOS apps John Doe certificates John Doe 1st app certificates > aps_production and Mobile Provisionning Profile for John Doe 1st app must be stored here after you have created them screenshots Create The Screen Shots You will need some screenshots to fill out the app sheet on itunes. You will be able to make them with Xcode and especially with the ios Simulator delivered with Xcode. Open the xcode project that is in the ios_source folder (see in the video when opening the project with Xcode), then choose the target, iphone 4s for instance, and click on the Play button:

12 Take some screenshots of the app for this target using CMD+S from your keyboard, and do it for each target you want screenshots. Before switching from a target to another don t forget to click on the stop button in Xcode. How To Be Sure The App Gets Accepted To be sure your app will be validated by Apple you have some tips to know (on Google Play there is no validation, so it s more easy): All your pages have to be filled out with content. Please be sure you have no empty pages. If you have a news wall feature for example, create a news, and with a picture it would even better.

13 Content: no explicit contents in your apps! But it was obvious ;) Design: please choose cool colors with complementarity. If you don t really know how to find colors with complementarity you can use But no rainbow apps, please don t. Features: Apple want useful apps. So don t create apps with only one or two features. And enter relevant content with multimedia (videos, images, etc) Write a good description of your app. You have to explain what the users would be able to find in your application, and why they have to download it. (250 characters minimum). Never talk about other platforms in your app! Apple doesn t want you to talk about Android or Google Play, or Samsung in apps that are on the Apple App Store. Even if there is a logo, or an image about an Apple competitor, your app will be rejected. If there is an account registration tab in your app, or part of your app that is blocked with the Padlock feature, be sure to provide test credentials to Apple in the Demo fields on itunesconnect.apple.com when publishing your app. Fill out the support policy url too. Never user test content in your app, like Lorem Ipsum content or test, demo, etc. Apple refuses apps that are not finished, and/ or apps for tests. Choose the right rating for your app. If your app is a Club app you have to set the rating to 17+ even if there is no photos, or products related to alcohol. Before compiling your app in Xcode be sure to deactivate the Audio Background modes if it s not an app about music. How To Publish Android App TO GENERATE THE APKS If you don t have already installed the APK Generator please click here to see how to install it at the bottom of the article).

14 Note that if you don t have a dedicated server you can t install the APKs generator, and when you will download the Android Version you will get the source files to compile them manually. If you have the APK Generator installed, you can generate the APK files automatically from your backoffice by going in Manage > Applications, then enter in the app sheet, go down in the page and you will find the link Generate APK. Click on it and then refresh the page after a few minutes and your APK will be available to be downloaded. If you don t have installed the APK Generator, to manually generate the APK, follow these steps to generate it from the source files: First of all you need Android Studio to generate the APK. If you haven t already you will have to download and install it. Go to and then download the Android Studio v related to your OS, and install it. Then, go here and at the bottom of the page, in the SDK Tools only section download and install the SDK related to your OS.

15 Then, open Android Studio you ve just installed, and click on Configure : Then, click on SDK Manager:

16 You will see a list of packages, some are installed some are not. There are some items that are checkked and some that are not. In addition to the ones that are already checked, be sure these ones are too, if not, check them: Extra -> Google Repository 12 Google Repository 12 Google Play services 20 In Android (API 19) > SDK Platform ARM EABI V7a System Image Google APIs (ARM System Image) Tools > Android SDK Build-tools 19.1 Then click on the install x packages button:

17 Then, click on every license and choose Accept License, and then Install:

18 Voila, your Android Studio is ready to create the APKs. Okay now, let s see how to create these APKs. Note: don t forget that you have to filled out the Android Push keys for your backoffice prior to create your APK if you want to be able to send push notifications. First unzip the folder with the Android sources which is named android_source.zip. Go back to the main menu of Android Studio:

19 Click on Import Project. You will see a warning message, don t worry about that it is the normal process, click on Ok. Then choose the Android Source folder you have unzipped, and click on import. When your project is imported, from the left menu, click on your folder android_source and open the tree. Check if there is no warning on folder and files. Then from the main menu click on Build > Clean Project. Then Build > Generate Signed APK. Then, click next and you get this screen:

20 Depending if it s an update of an app already published, or a new app you want to publish choose: Create new, if it s a new app Choose exiting, if it s an update of an app already published In this tuto, we will choose the first case, but second case is almost the same. Okay, so you have chosen Create new. Now we suppose that you are someone very organized (if not already, take a look to the article about ios publication and organize your folders the same way), and thus that you have already create a folder for your app publication on your computer. Before having downloaded the android sources, you have created a folder on your computer named My Awesome App, for instance, with two subfolders: one for the graphic items, like screenshots of this app, and one for the certificates which will be named certificate. Thus, on your computer we have a folder named My Awesome App with the subfolder certificate and the other subfolder graphics.

21 Okay now let s go back to Android Studio. You have clicked on Create new, and you get this screen: Now click on the button to browse in your computer folder and go to the certificate folder, in the main folder My Awesome App, and below in the File name field, enter certificate, and click ok:

22 Now click on the button to browse in your computer folder and go to the certificate folder, in the main folder My Awesome App, and below in the File name field, enter certificate, and click ok:

23

24 Enter a password for the key:

25 Set the Validity to 99 years, and enter the name of the app owner. Then click Ok. In the summary screen click next :

26 Then in the next screen, choose release for Build Type and then click on Finish. Your APK is built. NOTE: You can have some problems generating the APK for apps with name in other alphabets than the latin alphabet, like arabic alphabet, cyrillic alphabet or others, or problems with app name beginning with numbers. In these cases, you should do the following: Change the app name in your edition Download the sources Rename your app in your edition with the name in your language Open the project in Android Studio and on the left open the folder app>src>main>res In each values folder, double click on the file name strings.xml, in it you will be able to change the app name by the one in your own language. Then save the strings.xml file. Once you have done that in each value folder for each language, you can begin the creation of your APK.