3 ways to generate money from your mobile apps

Picture1.pngThe trend for revenue generated from mobile apps is constantly growing and is projected to reach $188 billions for the year 2020 (according to statista).

Today, I want to discuss the three most common options to generate money from apps and which you can already make use of if you have some traffic. I won’t include business specific solutions or selling of physical products outside of apps. So what are these three options?

 

1. Paid Apps

This requires the developer to publish a Paid app into the App Store or Playstore. It is most commonly used for apps by high profile company or apps which the customer already know what to expect from.

 

2. In-app Purchases

There are 3 types of in-app purchases:

Subscription – The user will either need to pay a monthly/yearly subscription feeAt the end of subscription period the user will have the option renew paid service. Note that, you can also allow the user to have trial periods (e.g a week) before a required subscription to continue to use the app.

Consumable – These are features within the app which the user is required to pay every time he wants them. The purchased item will get “consumed” at some point in time inside the app. Then the user will decide if he wants to pay again to get back the consumable item. An example of this would be buying extra-health in a game.

Non-consumable – These includes purchases which the user is expected to make only once in your app. After the purchase, the non-consumable item can be use at any point in time and on any other devices with the same Apple ID/Google Account. Some examples includes: “Upgrade an app to pro edition”, “Remove ads”, “full game unlock”.

 

3. Ads

Now the third option is to display ads inside of you app. There are 3 format of ads commonly used for mobile apps:

Banner ads – are rectangular images or texts that occupy a specific spot inside your app screens. They normally stay on screen while users are interacting with your app.

Interstitial ads – are full-screen ads that cover the interface of your app. They’re displayed at natural transition points in the flow of an app, such as during the pause between levels in a game.

Rewarded video ads – are full-screen video ads that users have the option of watching in exchange of in-app rewards.

 

Conclusion

As you can see, there is a high amount of money being consumed from within of apps. When designing a new app, do take these into consideration to make sure you have a successful business.

Cheers.

 

Material Design: the Shared View Transition

Material design is a comprehensive guide for visual, motion, and interaction design across platforms and devices. Android now includes support for material design apps. To use material design in your Android apps, follow the guidelines defined in the material design specification and use the new components and functionality available in Android 5.0 (API level 21) and above.

Why Material design?

Following Google Material Design guidelines is trivial to make sure your app is up-to-date with latest trends and is following proper design standards. Android users are also getting used to Material Design apps and will thus be feel more at ease with your apps.

Shared View Transition

Shared View Transition is one of guidelines mentioned from Material design when dealing with transitions between Activities (different screens). Essentially, you will only use this if you have some Views (images) which are present in both the current activity (screen) and the next activity (screen).

On implementation level, you only need to specify common Views (e.g an imageView) which is visible in current and next Activity (screen). Android will perform a transformation (e.g transition and scaling) such that the images will seem to move from the current activity to the next. Let’s see an example below before we continue on its purpose:

Purpose

The aim behind the share view transition is make the transition look seamless. E.g when loading a new Activity (screen), we may need to fetch some data from API and/or show a different Layout/UI. Showing a Slide in/Fade transition is an easy way hide this process but this transition is a bit rough. The user will feel like he going to a new screen. In worse case, he may even think he is going to a new app!

To sum it up, the Shared View Transition blends in the transition from one to another screen by sharing common Views or images. There is a lot more to read on the Google Material Design website with regards to transition: https://material.io/guidelines/motion/material-motion.html#material-motion-implications-of-motion. Please have a look if you haven’t already.

Implementing

Let’s go ahead with it’s implementation. Let’s say we want to share an ImageView between two Activities. (Note that that it could be any View e.g, a RelativeLayout.)

Add Transition Name to the layout files

  • Current Activity Layout – add transitionName for the ImageView which should have transition effect
<ImageView
    android:id="@+id/img_calling_transition"
    android:layout_width="90dp"
    android:layout_height="50dp"
    android:layout_alignParentTop="true"
    android:transitionName="my_img_transition"/>
  • Next/Calling Activity Layout – add same transitionName for corresponding ImageView which should receive the transition:
<ImageView
    android:id="@+id/img_receiving_transition"
    android:layout_width="120dp"
    android:layout_height="80dp"
    android:layout_alignParentBottom="true"
    android:transitionName="my_img_transition"/>

Pass Scene to Intent (in Java)

“StartActivity” call with ActivityOptionsCompat bundle. Create a Scene passing in View which will be transition along with the transition name.

    ActivityOptionsCompat options = ActivityOptionsCompat.
            makeSceneTransitionAnimation(getActivity(), (View) imgCallingTransition, "my_img_transition");

    Intent intent = new Intent(getActivity(), MgProgressStep2Activity.class);
    this.startActivity(intent, options.toBundle());

That’s it. You are done already.

Conclusion

The shared view transition is very easy to implement. Behind the scene, android does the transformation ‘effect’ for us such that the ImageView from the first activity is transformed according to the size and position of the new ImageView in the calling activity and we have “Shared” image transition effect. The result is a more seemless transition which result from applying shared view effect.

This post was quite basic but I feel like this transition is a bit underused (at least in my past projects). Shared View transitions is recommended by material design specifications and is easy to implement transition. So go ahead and use it when applicable. Thanks. Leave a comment if you got any issue with it’s implementation. Click on follow button on side menu to get notified for next post.

Cheers

Catch you in the next one.