Android Theme.AppCompat usage

Forum|Forum|7 years ago
November 5, 2018
1 reply
647 views

Hello,

we are using simple AltertDialog for our game (source), but for featuring, Google don't like it and as a result of review they write us:

Regarding the use of the outdated theme (Holo UI), yes we would require that all activities to inherit from Theme.AppCompat, Theme.Material, or one of their descendants. All native UI elements must use styles from the Material/AppCompat palette (e.g. Widget.Material…, Widget.AppCompat... or ?android:attr/...). Failing to adopt the new theming or design patterns can cause users to perceive the app as dated or non-standard.

Is anybody there already using the modern themes? Do I understand it well, that I must include the support library (with dependencies) and all the resources? It looks like quite bloat as it could be several MB just for simple yes/no dialogs:/

This topic has been closed for replies.

L

Leo Kanel

Inspiring

We use the latest dialogs ANE from Distriqt. That way you can have the latest device theme. However, you need 2-3 extra dependencies for it.

OldesAuthor

Inspiring

The thing is, that I want to avoid need to include all the JARs and XMLs, if they are not needed. We use system dialog just when user press BACK button, which Google wants us to use to quit the game, or when game is going to open web or app store page. It could be done as a dialog directly in AIR, but than we would need to take care of rendering of the multilingual texts, which we wanted to avoid.

So far it looks, I could just include AppCompat resources without classes (which is like 606kB) and use these as a base theme for the dialog. Still I have a very bad feeling of it, because the dialog is just 1 or 2 sentences with yes and no buttons.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded