From an idea to Google Play

Agenda

• Before you start developing.
• During development
• Making it a minimal viable product.
• Post development
• Post deployment

Pre development

• Market research
• Package name
• Native approach
• HTML5(web based) approach

Market research

• Take notes
• Compare features
• Read comments
• last but huge, use similar apps

Package name

• One time choice
• Make sensible choice
• Should reflect your company / website

Native approach

• High speed, slow development
• Android version
• API level
• Supported form factors
• Use case: Contactbook

HTML5 approach

• Low speed, faster development
• Native apps using frameworks
• HTML5 apps using frameworks
• Use case: Inventory tracker

During development

• Taking care of ANRs and NPE.
• Exception prone areas more failsafe
• Remote error logging
• Offline capabilities
• Performance & Security
• Best practices

ANRs and NPE

Avoiding ANRs and NPE

• Respond to user within 5 seconds
• BroadCast Receiver must complete within 10 seconds
• Users perceive lag longer than 100-200ms
• Use Threads and AsynTask within Service
• Be cautions with Preferences or Account Managers

Failsafe exceptions

            // Bad practice
            try{
              // do something risky
            } catch (NarrowException1 e){

            } catch (NarrowException2 e){

            }
          

            // Good practice
            try{
              // do something risky
            } catch (NarrowException1 e){

            } catch (NarrowException2 e){

            } catch (Exception e){

            }
          

Remote error logging

            try{
              // do something risky
            } catch (NarrowException1 e){

            } catch (NarrowException2 e){

            } catch (Exception e){
              // call error API
              // for remote logging
              // on server
              error( e.getMessage() );
            }
          

Offline capabilities

Performance & Security

• Use Logging cautiously
• Log.d or Log.v for sensitive info
• Let the runtime kill the Service
• Avoid creating objects
• Use cloud to device messaging
• LBS update frequency should be 5min
• LBS update distance should be 1000m

Minimum viable product

• Google Analytics
• Admob integration
• ACRA integration

Google Analytics integration

            // Start tracking
            tracker.start("UA-MY_CODE-XX", this);

            // Register an activity view.
            tracker.trackPageView("/map_activity");

            // send views to server
            tracker.dispatch();
          

Google Admob integration

            // Create adview
            AdView adView = new AdView(this, AD_TYPE, 
            MY_BANNER_UNIT_ID);

            // Create an ad request
            AdRequest request = new AdRequest();

            // Load ad in the UI.
            adView.loadAd(request);
          

ACRA integration

            // Associate the form
            @ReportsCrashes(formKey = 
            "tWTBQaGdDI4V1YDgzWHVqQWc6MQc2ZVZRb")

            // Initialize ACRA
            ACRA.init( this );
          

ACRA usage modes

• Silent (default)
• Custom server script
• Email
• Almost anywhere, by implementing a simple interface

ACRA report desitnations

• GoogleDocs Form (default)
• Toast
• Notification
• Dialog

Post development

• Testing over production build
• Three things to remember
• Publishing the app

Testing over production build

• Atleast last 5 version should be considered

Three things to remember ALWAYS!

• Signing key
• Package name
• Version name / number

Publishing on Google Play

• Targets 1906+ device models
• Indian developers can now sale apps
• Keep description brief and concise
• Attractive banner (1024x500)
• Screen shots (320x480,..)
• App icons (512, 96, 72, 48, 36)

Post deployment

• Collecting feedback
• App updating interval
• App stores to publish the app on
• Leverage social

Collecting feedback

• Google Forms
• Custom application rating activity
• SurveyMonkey.com
• PollDaddy

Application updates

• Right away for critical crashes
• UI issues can be delayed
• 30-40 days is ideal
• Too frequent updates irks user

Third party App Stores

• Opera Mobile Store
• GetJar
• Blackberry runtime for Android
• OpenAppMkt
• SlideME

Leverage social

• Make heavy usage of social network
• Respond to users
• Get feedback
• Promote application and grow your community

Some numbers

• Every time a new app is downloaded, the usage of all other apps on the device, decreases by 19%.
• On an average a user has 41 apps installed on his device
• 63% of time is spent with social apps. #AppsWorld

1.3mn activations daily

Questions ?