Chrome dev tools to emulate mobile devices with navigation bar - android

Hey I'm a web developer and I'm looking for a way to emulate mobile devices which also displays their respective navigation bars, toolbars etc. In the 'Device toolbar' in Google Chrome (v58 on macOS) there's a specific mode available for the Nexus 5X (and 'supported devices', according to Google), which is exactly what I'm looking for (see screenshot below), however I can't seem to find a way to turn this on for other devices (such as iPhones, Galaxys etc).
Of course these bars would differ between the devices and the browser that it's running, so ideally I'm looking for a way to manually specify the height of the bars and how they interact with the viewport (e.g. iOS Safari includes the top bar in the viewport height calculation but leaves out the bottom bar, which kinda screws with how the bottom of the page is being displayed (as discussed here)).
Ultimately what I'm trying to achieve is a way to accurately simulate how a website would look on a specific device, by instead of looking at just screen sizes and pixel density actually taking in to account that there are other sections being displayed on the screen which of course takes up screen realestate themselves and affect the appearance and user experience.
All ideas are welcome =)

You can use Blisk browser, it's built on Chromium and supports toolbars and panels for IOS/Android devices, it has a good set of devices that you can emulate on.

Related

How to make app UI to work 100% same on all devices?

How to make sure that my App's popup or text appears exactly how I intended it to appear in all screen sizes? I want the aspect ratio of the popup to appear same and all the text that appears at the time of designing the popup to be same in all the devices.
Imagine an image who's size and content will be same across devices. But for some reason I can not use image here, the requirement is to use popup with text and butto. I dont want any screen to cut the popup or make the text of the popup disappear or turn to crap.
I can not do testing with one device at a time as I read on a site that there are over 10,000 android devices :|
Is there anyway or any tool part of Android Studio which can like quickly draw outlines of all the phones screen sizes to help me understand what aspect ratio is right for my popup?
Im a noob so my question may not make sense to you so please bear with me.
Unfortunately it's going to be nearly impossible to get things to appear 100% the same across all devices and browsers – Android runs on all sorts of devices and there are probably hundreds or thousands of different possible screen sizes, in addition to browser and operating system quirks. Start with identifying specific devices and screen sizes you wish to support. See Android's screen compatibility overview for some good information on this topic.
If possible look at user analytics to narrow down the most common devices, operating system versions, and browsers, then test against those.

How to fix app bar being covered by bezel?

I was just testing my app on Pixel3 XL emulator and noticed that the app bar is covered by the bezel. I thought the flutter framework handles this for app bar own its own.
Is there a way to fix this? I also looked at SafeArea but that probably would make me to manage the app bar on all the pages of BottomNavigationBar.
This is an issue with the emulator, not Flutter. If you open Chrome on the emulator you will see that it's also covered by the notch. You can also drag from the notch and the notification's pane will be dragged down, even thought it shouldn't be possible.
You can fix this though. Open the Android settings, go to to the About phone section and tap on the Build Number 7 times, to enable developer mode. Once that's done, in Settings, go to the System section, open Advanced and go to Developer options. Tap the Display cutout option and select Tall cutout. This will adjust the OS to account for the notch.

Native mobile browser select element options count

How many options from a standard select element fit on the portrait-oriented screen of a given popular device?
For example, my Pixel 2 fits 9 options (9.5, but I'm looking for wholly visible options)
The purpose of this question is that I have a drop down selector where I don't really need to display all of the options, but more is better. I also think that not having the user scroll is advantageous. I'm trying to find a happy number where I can display the most options without causing those options to overflow the device height.
Since I only have the one mobile device, and nowhere is this data readily available, I'm turning to you.
My iPhone X legibly shows 7. My iPad shows a bunch. Easily 15 depending on where the dropdown is in the screen, since it's more of a desktop style.

android Accessibility screen magnifier

I would like to create an Android Accessibility Application/Service.
This Accessibility app would be able to magnify any screen image produced by any application resident on the android device.
for example, I would like to be able to magnify...
the home screen
Settings menu and sub menus
I would like to magnify Text and images/icons etc..
I've googled and searched the android dev docs for hints/tips/ideas.
Sadly I've hit a dead end.
Is this type of Accessibility application impossible to develop on Android?
Jellybean - Android 4.2 - apparently has this functionality built-in - see this release article detailing new features in Jelly Bean: "Accessibility: Enable screen magnification to easily zoom or pan the entire screen to get a closer look. Visually impaired users can now enter full-screen magnification with a triple-tap on the screen"
Typically on mobile operating systems these features are built into the OS, and not something that a 3rd party can write; partly for security reasons (a magnifier would have access to the graphic output of other apps, so could in theory send screenshots containing sensitive information back to base on the sly) and partly because magnification is complex, in that it involves interfering with normal video output and also with touch input (touch input has to be scaled in the inverse way that the original graphics area, so that touching a magnified button goes to the right place).
There may be a way of doing this if you are prepared to root your device and poke around at the OS/driver level, but that's not going to help much if you want an app you can put in the store.

Android device guidelines/requirements

Are there any requirements/guidelines for an Android device? like numbers of buttons or minimum buttons required.
Also are there any android devices which do not have the menu and back buttons?
( I am aware that no menu/back buttons will kill most of the apps in terms of usability , I just wanted to know more on the topic :-) )
Are there any requirements/guidelines
for an Android device? like numbers of
buttons or minimum buttons required.
Yes. These are documented in the Compatibility Definition Document.
Also are there any android devices
which do not have the menu and back
buttons?
That depends on how you define "buttons" and "android devices". Quoting from the CDD (see above link):
The Home, Menu and Back functions are
essential to the Android navigation
paradigm. Device implementations MUST
make these functions available to the
user at all times, regardless of
application state. These functions
SHOULD be implemented via dedicated
buttons. They MAY be implemented using
software, gestures, touch panel, etc.,
but if so they MUST be always
accessible and not obscure or
interfere with the available
application display area.
There are devices that do not have dedicated off-screen buttons (whether physical or touch-sensitive off-screen spots). The ARCHOS 5 Android tablet is one -- it has the HOME and BACK buttons in an expanded title bar. However, it is unclear if Google considered them to have met the CDD, since the ARCHOS does not have the Android Market. Devices lacking the Market may not meet the CDD.
So, it is entirely possible to create devices that do not meet the CDD, but at that point Android is mostly just another embedded OS, IMHO.
I would recommend this links:
Twitter for Android: A closer look at Android’s evolving UI patterns
Android UI design patterns
User Interface Guidelines

Categories

Resources