How Optimize Your Android Apps For Chromebooks Became A Globally Well-Known Brand
As more Chromebooks are enabled with Google Play, it's a
good time to optimize your Android app for Chromebooks to reach a wider
audience. The changes in the giant screen optimization will benefit mobile
devices capable of designing on desktop monitors, such as the Samsung Galaxy
S8. The current list of Chromebooks that can access the Play Store continues to
grow.
There are several differences to consider when optimizing
your Android game or game for Chromebooks:
- Higher screen sizes and higher resolutions
- Multi-window support and resizable windows
- Different methods of hardware input: keyboard, trackpad, mouse, pen
- Chromebooks to use tablet and laptop modes
- Chromebook users can change screen resolutions, switch between different input methods, and convert from laptop to tablet mode at any time, so that Android applications and games can handle all these situations with elegance.
Discovery on Google Play
If Android apps or games require hardware not available on a
Chromebook (such as mobile or GPS functionality), these titles will not appear
on Chromebook users such as Play on Android tablets. Developers should maximize
discovery on Google Play by doing the following:
Set the permissions and features used in the manifest to
ensure compatibility with Chromebooks. Not all Chromebooks will have touch
screens, GPS or rear cameras that are typical for smartphones. Update the
manifest so you do not need sensors and hardware that are not found on
Chromebooks. example:
<use-feature android: name =
"android.hardware.touchscreen"
android: required = "false" />
In addition, to educate Chromebook users on all of the
specific Chrome OS features that have been implemented, for example, by
supporting additional input methods such as keyboard, trackpad and pen, or
through high-resolution support screens with a reactive layout, developers
should update the description app on Google Play. It would also be helpful to
provide screenshots with how the application or game works on the larger
screen, or how the title works on a particular Chromebook.
Feature optimization
Large screens and resizable windows
Chromebook users will be more likely to perform various
tasks, opening multiple applications and / or games at the same time, taking
advantage of screen size and operating in a manner compatible with a desktop or
laptop form factor. Unlike Android phones, they can also change the screen
resolution to fit the screen, or enlarge fonts, UI and graphics if necessary.
Multiple window support and fully scalable window support are the key to this
use. Graphics, fonts, layout, and touch targets should be adjusted accordingly
when screen resolution and orientation change.
It is also important to note that just because an
application or game window is not focused, it does not mean that it is not
visible. For example, if a video application is open in an inactive window, it
should continue to play content "in the background" because it may
still be visible throughout another application window. To fully support the
use of multiple windows in this case, pause the video in onStop () and continue
inStart ().
Targeting Android N (API level 24 and above) will notify the
Google Chrome window manager that compatibility restrictions should not be
used. This allows more flexibility and control over the developer side to
support window resizing.
The system supports window management if Android N is
directed, but to support the pre-N API, Windows can be toggled between the
default size selected at application startup or in full-screen mode with the
window bar visible or with hidden window UI in an immersive full-screen mode.
When handling different window modes, it is important to
know that the window area of an application or game window will be compensated
for by the presence or absence of the window control bar. The application
should not assume that the activity will always be (0,0) in the window. Adjust
the layout and assign the goals accordingly.
It is quite common to see that
apps or games no longer respond after a window resizing or orientation change
because you did not manage the presence of the window control bar or the
resolution settings plus Chromebook High View. Orientation support Because of
the laptop's form factor, Chromebook users feel that the landscape is the
default orientation for Chromebo applications oks.
VIDEO 1.1 ANDROID TRAINING IN REVIEWS
However, Androidapplications often assume that portrait is the default orientation to support,
because of how users interact with their smartphones. To provide flexibility to
users, it is strongly recommended to support portrait and landscape
orientations. Some Chromebooks are convertible, so users can switch between
tablet and tablet modes at will, switching between vertical and landscape
orientation, adjusting what feels comfortable for a specific use case.
Most importantly, if possible, it does not need to be
restarted if the orientation or size of the window changes. If a user is
filling out a form, creating or editing a certain content or in the middle of a
level in a game and losing their progress due to a window change - intentional
or not - it would be a weak user experience. Developers can monitor window
configuration changes using onConfigurationChanged () and dynamically manage
these changes by adding this line to the activity manifest: android:
configChanges = "screenSize | smallestScreenSize | orientation |
screenLayout".
If it is absolutely necessary to require a restart on the
changes made in the window, at least the restore state using the
onSaveInstanceState () method so that the job or status is not lost. In
addition, it is important to be consistent with the application's orientation
when the user navigates through the activities. Currently, the system forces
Android applications to follow the orientation of the root activity to maintain
consistency.
However, this may
cause a situation where an application may start in landscape orientation, and
a login screen normally set to portrait orientation appears and does not appear
to be optimized due to a non-responsive layout. In addition, it is still
possible to have a case where a trampoline activity begins in a different
orientation from the main orientation of the application. Keep these possible
scenarios in mind when designing the layout of activities. Ultimately,
developers need to be aware of the differences in camera processing and focus
on Chromebooks.
Obviously, Android phones have forward and backward facing
cameras that are located at the top of a screen facing the portrait.The frontend cameras on Chromebooks are located at the top
of a landscape-oriented screen. Many Chromebooks do not have backward-facing
cameras. If an application requires a camera, it would be better to use
android.hardware.camera.any to access the front camera if a back panel is not
available. Again, developers should target Android N and, if possible, allow
the application to be scalable so that the system can handle the correct
orientation of camera views.
Support for multiple input methods Chromebook users are used
to interact with web pages and applications using a keyboard and trackpad.
Effective support for both input methods for an Android application means:
Support for keyboard shortcuts for commands that a desktop user might be
familiar with. Use the arrows and guides and a touchpad to navigate an
activity. Open the panel and open pop-up menus.
Support other
trackpad gestures to improve desktop productivity / portable mode Something as
simple as returning to send text in a messaging application or allowing a user
to navigate the fields by pressing the tab button, an application will feel
more efficient and consistent in a Chromebook. Even though there is a
compatibility mode for Chrome OS to mimic touch screen scrolling and other
touch events, it would be better to opt
Comments
Post a Comment