Mobile Programming Lecture 19

1. Mobile Programming Lecture 19 Publishing to Google Play

2. Agenda • Preparing Your App for Google Play • Positions with The Mobile Lab

4. Publishing to Google Play What are some things that you think should be done before you publish to your app to Google Play?

5. Debugging • We've covered debugging previously • If you don't know how to debug at this point, that's my fault.

6. Preparing Your App Test your application extensively on an actual device • —JUnit and other test cases. • UI/Application Exercise Monkey

7. UI/Application Exercise Monkey • The Monkey is a command-line tool that you can run on any emulator instance or on a device • It sends a pseudo-random stream of user events into the system, which acts as a stress test on the application software you are developing.

8. UI/Application Exercise Monkey • The Monkey includes a number of options, but they break down into four primary categories: • Basic configuration options, such as setting the number of events to attempt • Operational constraints, such as restricting the test to a single package • Event types and frequencies • Debugging options

9. UI/Application Exercise Monkey • If your application crashes or receives any sort of unhandled exception, the Monkey will stop and report the error • If your application generates an “application not respondingerror”, the Monkey will stop and report the error

10. UI/Application Exercise Monkey e.g. $ adb shell monkey -p your.package.name -v 500 Command Options

11. Preparing Your App What do you think are some Things That Cannot Change after you first publish an app to the market?

12. Preparing Your App Choose a good package name! Things That Cannot Change

13. Preparing Your App Test your application extensively on an actual device • —JUnit and other test cases. • —UI/Application Exercise Monkey • Obtain one or more physical devices • —Run it under realistic network conditions • —Can verify that the UI elements are sized correctly • —Can check that your performance and battery efficiency are acceptable • —Testing your Application

14. Preparing Your App • —Consider adding an End User License Agreement in your application • To protect your person, organization, and intellectual property, you may want to provide an End User License Agreement (EULA) with your application • http://bees4honey.com/blog/tutorial/adding-eula-to-android-app/

15. Preparing Your App • —Consider adding support for Android Market Licensing • This is optional. • —If you are publishing a paid application through Android Market, consider adding support for Android Market Licensing.

16. Preparing Your App • —Consider adding support for Android Market Licensing • With Google Play Licensing, your application can query Google Play at run time to obtain the licensing status for the current user, then allow or disallow further use as appropriate • an application can • check the licensing status and then apply custom constraints that allow the user to run it unlicensed for a specific validity period • restrict use of the application to a specific device, in addition to any other constraints. • More on Licensing

17. Preparing Your App • —Specify an icon and label in the application's manifest • The icon and label that you specify in an application's manifest are important because they are displayed to users as your application's icon and name • —They are displayed on the device's Home screen, as well as in Manage Applications, My Downloads, and elsewhere. • Additionally, publishing services may display the icon and label to users. • —Define the attributes android:icon and android:label in <application> element in the manifest.

18. Preparing Your App • —Before you do the final compile of your application • Version your application • Before you compile your application, you must make sure that you have defined a version number for your application, specifying an appropriate value for both the android:versionCode and android:version Name attributes of the <manifest> element in the application's manifest file. • Carefully consider your version numbering plans in the context of your overall application upgrade strategy. • If you have previously released a version of your application, you MUST make sure to increment both the Version Code and Version Name Attributes. • —Versioning your Application

19. Preparing Your App • —Before you do the final compile of your application • Version your application <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.example.package.name" android:versionCode="2" android:versionName="1.1"> <application android:icon="@drawable/icon" android:label="@string/app_name"> ... </application> </manifest>

20. Preparing Your App Next, you need to • Obtain a suitable private key • Compile your application in release mode • Sign your application with your private key • Align the final APK package Do you want to learn how to do this via the command line? • Signing your application

21. Preparing Your App To do this in Eclipse • File > Export > Export Android Application To get an idea of what values you should enter in the form, look at the sample values used on the command line here

22. Preparing Your App Preparing for Release

23. Mobile Lab Positions Interested in working for the Mobile Lab?

24. Do you have what it takes? • The Mobile Lab is looking for interns for this coming fall • If you are interested in working for The Mobile Lab • Send resumes to gt10e@my.fsu.edu • Candidates selected for interview • Interviews conducted during the 1st and 2nd week of classes • Candidates notified about interview results

25. Do you have what it takes? • These are unpaid positions in the Mobile Lab, but it's a great opportunity to earn experience! • I will not be interviewing anyone in this class • Feel free to send me your resume and ask me for advice on how it can be improved and tailored for The Mobile Lab