SUNDAY TICKEY UPDATE
SUNDAY TICKEY ANDROID

If your game relies on additional asset downloads, you'll need to build your own solution if you currently rely on Google Play's asset delivery.Ĥ. This is necessary partly because of the new bundle IDs you'll be using and partly to ensure you can properly analyse and attribute data.ģ.Ěsset handling. In-app advertising, in-app analytics and attribution or the set-ups if you work with a mobile measurement partner (MMP).

SUNDAY TICKEY UPDATE

Not all stores support effective auto update features, so you may need to be prepared to enhance your own in-game messaging and trigger users to manually update.Ģ.

Things you'll need to think about include:ġ. You will also need to factor in how stores drive updates into your feature planning. Payments will be the biggest change you'll need to make to an existing game, but there are other important factors. Take time to understand each store - they all have quirks which you must cater for if you are to deliver a solid user experience. The processing time for purchases may be different as may the way conditions are handled. Make your payments handling robust - payment systems behaviour varies across stores and will be different to what you're used to in Google Play.

Some stores may mandate their own login / account features to be added.

References or linking to other stores are not allowed.

Stores require a separate bundle ID / package name compared to Google Play.

Plan for the differences from the outset.īeyond technical requirements (like adding the store's own payments), there are several operation requirements that crop up in all the alternative stores. Build an understanding for all target channels' requirements right up front. Even then, it may be useful to understand the best way to go about things.

In-app advertising – fill rates may be lower, and campaigns may not convert if they rely on Google Play for downloads (as Google Play isn't present on the devices)Īt this point, you may already be thinking about working with a third-party expert to help your games reach the alternative app stores.

This means you'll need to look at how you've implemented:

SUNDAY TICKEY ANDROID

There is a second batch of pain driven by new flavours of Android which lack support for Google Mobile Services (Amazon's Fire OS devices and newer Huawei devices run Android without any Google powered apps or features).

Attribution across not only multiple campaigns and networks, but also to multiple campaign endpoints.

User experience and flows to manage store-specific quirks.

In-game asset management and hosting (if you rely on downloadable assets post-install).

In-app payments (IAP) – most stores mandate their own payment systems or require you to bring your own billing.

Soon you will be publishing not just in one store, but in several. The first batch of pain comes from fragmentation driven by new commercial and technological requirements. There is always a checklist of things to consider. However, the alternative app store space is big so if you do want to go it alone, here are a few tips for you that will hopefully make your journey smooth and successful. There are all sorts of pain points relating to moving to new app stores. This is potentially a lucrative revenue stream… and it's for a game or games you have already developed.

Huawei's App Gallery, the Amazon App Store, the Samsung Galaxy App Store, Xiaomi GetApps, and the One Store can bring you whole new audiences, users, you've heard, more likely to make in-game purchases. But the same game can succeed on other app stores too and that's tempting. You have an Android game and it's working out fine on Google Play.

Sunday tickey