Can anyone tell me what is the difference between multi-window and and multi-display in the AOSP environment.
multi-window
devices can display multiple apps simultaneously using multi-window. Android supports three multi-window configurations:
Split-screen is the default multi-window implementation, which provides two activity panes where users can place apps.
Freeform allows users to dynamically resize the activity panes and have more than two apps visible on their screen.
Picture-in-picture (PIP) allows Android devices to play video content in a small window while the user interacts with other apps.
https://source.android.com/devices/tech/display/multi-window
multi-display
Devices can now have multiple physical displays and inputs. Example: Two people can use the same Android device via two different displays at the same time. This is a new feature to Android Q and comes with a ton of limitations so far.
https://source.android.com/devices/tech/display/multi_display
Related
I am doing some compareson between Smart TV platforms way to develop applications and I wonder if Google TV applications only are available in "Full screen" mode? In other words taking up the whole screen.
Samsung Smart TV have three different application layouts available, see link: http://www.samsungdforum.com/upload_files/files/guide/data/html/html_2/getting_started/intro_to_samsung_smarttv_apps.html
Full screen, Single-wide application and ticker. This specifyes how much space the application takes up on the screen so the user can for example watch tv while using the application, because the application only takes up a part of the screen.
I found this FAQ:
Can I use picture-in-picture (PIP) in my Google TV Android application?
No. The picture-in-picture (PIP) feature is only available for live TV. You can't use it in your Android application, nor can you run an Android application in the PIP window.
From that answer I want to say that Google TV applications can only be used in full screen mode. Am I right?
Thanks for helping
Yes they can only be run in fullscreen mode. That is to say only one app can have focus at a particular time. You can however make your app transparent for the most part to allow whatever is underneath it to show through. This post has a good solution Full screen transparent activity (no title & status bar) doesn't work.... why?
I am starting a project with PhoneGap and it will work on iPhone and Android devices. The question is how to implement support for different screen sizes and resolutions.
For example, I have an icon inside the application: small waves to run some action. What size of this icon should be to be shown well in all possible devices (iPhones/Androids). Should I include several versions of the same image?
The same question about text. How can I be sure the text will be readable and will stay in line on different devices?
thank you
If you are a MAC user you could give the new dreamweaver 5.5 a shot. It will structure your app and even build a debug version for testing. You can do this with either the ANDROID SDK or the iOS sdk. Of course, it will work on a PC as well but there is not support for the iOS sdk.
Using the Adobe Dreamweaver 5.5 it has specific mobile framework to recognize jqm or jqtouch and inserts phonegap.js on build into the packaged product. It also allows you to scale the testing screen for the different sizes of mobile devices. From android, iphone, to ipad(and more)
Here is an example: Dreamweaver with phonegap support
I am considering developing an Iphone/Android application but I want the information on it to be live and uniform between platforms... Therefore it seemed logical to me to make it web based. I would however like to be able to achieve certain non web based functions such as adding events to the calendar and gps locations on the the mapping sortware.
My questions are:
Can I make a web based
application that does not visually
show in a browser?
Can I add additional functions that
are not natively available in a
browser e.g <a href="#"
title="adddate:110911"/>Add to
Calendar</a>
Would it be a lot of work to make
such an app as the majority is web
based (I mostly progam in PHP so
coding for Android and Iphone will
take me some time to get my head
around).
All of the questions are for both Iphone and Android.
Thanks
I would recommend using a cross platform solution like phonegap (with UI sencha touch on top of it).
You can have an app that is a thin shell over the system browser, and exposes the non-Web bits of functionality to the contained HTML via JavaScript interfaces. You will still need two different codebases for iPhone and Android, but the essense of the app will be still webby.
There's no way to manage the system calendar from Web apps neither on iPhone nor on Android, AFAIK.
I have built a multi-touch application which is based on a Java EE backend and combined with BlazeDS to a Adobe Flex frontend. The application runs on a DIY-Multi-Touch which I built. Now I want to use another solution. The Adobe Flex frontend (with a multitouch library) and the BlazeDS adapter should be replaced by a solution which covers iPhone/iPad, Android and commercial Multi-Touch displays.
The problem is the iPad/iPhone, there is no Flash Player runtime (not the jail-breaked ones), but the application should be runnable also on those devices. So Adobe Flex and a Java frontend (no JVM on the iPhone/iPad) is not possible anymore. At first, starting the developing of the application it was not neccessary, to run it on Apples mobile devices, but this changed :-(
So, what can I do, using HTML5? So I can use it for Android and iPhone/iPad. But I also want to make it possible to use it on a commercial multi-touch-display and normal display with a mouse (I only have gestures for one finger, the 2-finger gestures are not neccessary). Are there any frameworks that allow this? Because I do not want to create several frontends (App for iPhone/iPad on Objective-C and a Adobe Flex for all other devices), it would be great if I can build a frontend for all devices.
Does anyone know how I could realize this?
Best Regards Tim
Take a look at Sencha Touch, it's a HTML5 framework dedicated to iOS and Android devices, which should make it relatively easy to build web apps that feel like native apps on those devices.
The Adobe Flex frontend (with a
multitouch library) and the BlazeDS
adapter should be replaced by a
solution which covers iPhone/iPad,
Android and commercial Multi-Touch
displays.
Android 2.2 and higher supports the full Flash Player, and therefore also supports Flex applications. However, Adobe has spoken of improving such support for the next Flex release, expected out early next year.
Apple has kind of specifically said they want to prevent the type cross platform development you're trying to accomplish.
Without knowing, or seeing, your application it is hard to say whether HTML5 will support you. But, yes, many parts of HTML5 should work across multiple browsers.
You may want to investigate Elips Studio which brings ActionScript applications to multiple devices including apple devices.
I'm looking at prototyping with a HTC Advantage, which runs Windows Mobile 5 and has a screen resolution of 640x480 (or the other way if in portrait).
Before anyone jumps in and suggests developing as a native Windows mobile app, we're prototyping as a Java midlet because we also want to find out what restrictions/limitations/design considerations there are if we decide to then take the code to run on other mobile platforms: Java allows us the largest mobile-base with fewer code changes.
I'm using Netbeans 6.8 for the development, and I can't see any way to change the "Device Screen" view of a midlet from a typical mobile-phone sized screen, nor change the view from Portrait to Landscape; similarly, the emulator doesn't have a large-resolution device.
I'm using the default mobile device of ClamshellCldcPhone1. I've looked at some of the other device profiles, but none of them seem to be targetting larger screen devices from what I can see. And I can't find any documentation that tells me the difference between, say, ClamshellCldcPhone1 and DefaultCldcPhone2.
Has anyone any experience of this? Most of the existing things I've read have said to design for the smaller resolution and use anchoring to ensure controls stay in place; however as I've got a screen that's twice the resolution, I want to write for that resolution (given this is currently in prototype world). I can copy the code over to the HTC device to test, but this will (probably) get painful, especially during the early stages.
Any advice welcome :-)
What you need is a new emulator configuration for your handset form factor.
The emulator in Netbeans is the same as the J2ME SDK (formerly Wireless ToolKit, hence the WTK acronym) from SUN Ltd.
You can make a copy of the ClamshellCldcPhone1 folder that is presumably located inC:\Program Files\NetBeans 6.8\mobility8\WTK2.5.2\wtklib\devicesand modify the images and .properties file in your new configuration to match the device you want to emulate.
You can add/remove physical keys, resize the screen and make it touchscreen that way.
This should all be explained in the J2ME SDK documentation.
It's been a very long time since I did any of this, but I think you can just copy one of the existing profiles, rename it, and change the settings to what you want.