Adding power to your Android distribution: Eight app stores or more in 30 minutes

Preview:

DESCRIPTION

Developers are used to using a single distribution channel for their Android applications. Yet submitting apps to only one store, even if it's the market leader, significantly limits the app’s potential user audience. On the other hand, uploading an app to multiple stores can be time-consuming and complicated, especially when it comes to having to integrate in-app purchase into your app for each new store. In my session I will tell you about useful open-source tools, which will make your cross-store app publishing a breeze, and show you some coding technique for a fast and easy in-app purchase API integration. As presented in DroidCon Tel Aviv 2014 by: Anastasia Karimova, Yandex http://il.droidcon.com

Citation preview

Adding power to your Android distribution: Eight app stores or more in 30 minutes

Anastasia Karimova, Android developer

The biggest Android app store

2

Current number of Android apps in GP

3

* Source: AppBrain.com (05.06.2014)

1 242 915*

4

5

Available not everywhere in the world

Android ecosystem

6

GMS package

Basic

Russia: Credit card? No, thank you!

7

Limitations of GP

8

Strong competition

Limited set of supported countries

Limited carrier billing

GMS restrictions

10

* Amazon data

Amazon: available in 200 countries*

11

* SlideME data

SlideME: preinstalled by 140 OEMs *

12

* T-Store data

T-Store (Korea):20M users,1.2B downloads*

Why publish anywhere else?

13

Don’t miss devices without Google Play

Get better app discoverability

Get larger geo spread

Get additional payment channels

Let’s do it?

Get ready for some time consuming challenges:

in-app billing

appstore publishing

14

One Platform Foundation

Open In-app Billing

A single in-app billing API

17

In-app purchases

Before

18

Yandex.Store

Your app

19

Google Play IAB SDK

Google

20

Amazon IAB SDK

Amazon

21

Samsung IAB SDK

Samsung

1. Samsung In App Purchase v2.0 IAP (In-App   Purchase)   v2.0   lets   you   use   Samsung’s   payment   services   inside   apps. While v1.0 linked to the library jar file, v2.0 uses the AIDL (Android Interface Definition Language) to help the IAP process and applications communicate with each other. The latter makes it easier to link than the former.

1.1 Product Purchase The below figure shows the process where an application uses IAP to request the purchase of a product.

① Proceed with the Samsung account authorization process. ② Bind IAPConnector to enable the IAP API. ③ Call the init() method start resetting IAP and receive the results as a bundle.

22

T-Store IAB SDK

T-Store

!화를 이용해 용품들을 구입하시고 어플의 추가 옵션들을 시도해 보세요!

화를 이용해 용품들을 구입하시고 어플의 추가 옵션들을 시도해 보세요!

250 Kb

After with Open In-App Billing

23

Open protocol

OPEN!STORE

Basic principles

24

As close to Google Play in-app billing API as possible

One APK works in all app stores

Open in-app billing protocol

Let’s try OpenIAB

25

bit.ly/openiab

OpenIAB is already supported by

26

!

Need to solve app store publishing (time consuming)

27

Publish

28

Different  developer  consoles  

Each store – its own publishing rules

AppDF

A format to ease developer’s life

Application Description File

30

title

title

description.xml

title

description

what’s new

features

In-app-products.xml Binaries

APKAPK

APK

Benefits

31

Localization

AppDF Demo

32

onepf.org/editor/

Who supports AppDF

33

Use AppDF to submit your OpenIAB powered apps across multiple app stores

34

35

onepf.org

Thank you!

Recommended