I am developing an app for Android TV and need to make some decisions with regards to what minimum version to support. However, all the stats I can find about platform version distribution include mobile devices. Is there anywhere I can see statistics specifically for Android TV devices?
Related
Android Management APIs are supposed to be "compatible with any device running Android 5.1 or above that has Google Play installed." I really want that to be true, but am having trouble with Android TVs. (Specifically, a NexBox A95x and a TX3mini I'm testing with.)
My stumbling point is how to enter the enrollment token into the device when provisioning it? I had no problem with a Samsung tablet. But, the Android TVs don't use the same startup wizard after hardware reset, so there doesn't seem to be an opportunity to trigger a QR reader, or manually enter the token. I've tried entering the enrollment token into Google Play app (in lieu of the email or phone number to log in), but no luck.
Any ideas or insight how to make this work? If anyone knows a definitive reason why this can't be made to work (e.g. Management APIs don't work on AOSP) that'd be helpful information too.
Clarification (Updated 26 Dec 2017)
Here's a minimal, complete, and verifiable example of the Google Management APIs. The Quickstart exercise from Google, themselves.
Problem: The Quickstart exercise doesn't seem to work with Android TV (tested on a NexBox A95x and a TX3mini). The blocker appears on this step: (Provision A Device). The Android TVs have their own setup wizards that do not accept an Android For Work enrollment token. (I have completed the Quickstart on a Samsung tablet without problem.)
Google's documentation says the Management APIs are "compatible with any device running Android 5.1 or above that has Google Play installed" so it seems these Android TVs should qualify.
Has anyone found a workaround to do complete the Management API Quickstart on an Android TV?
As far as I know the Android Management API doesn't supports Android-based OS's like Android TV, Android Wear, Android Auto or Android Things. It just supports standard Android for phones and tablets.
I had my first Android TV app go live last night, but it has to be searched for in Google Play. How do you get your app listed in the Entertainment Apps section of the Home screen (and in the Google Play Store on Android TV) so people can actually find it?
It turns out that the Entertainment Apps section does not include all Android TV apps like I had thought. It is a curated list. So unfortunately that means Android TV apps have the same likelihood to be discovered as regular Android apps, and it makes the Andoid TV ecosystem look much smaller to the user than it (presumably) is. I guess I was expecting something more like Roku's channel store.
We have a peculiar problem if anyone has run into anything similar. We have a fairly large mobile app, built with Apache Flex 4.10 and Air 3.8. Runs beautifully on iOS. Screens are quick to load, scrolling is smooth and the app is almost desktop like. However, on an Android device, it runs painfully slow. Same codebase, both modern devices, everything same. It takes about 4 times as long to run on android as on an iOS device. Any ideas?
The issue turns out is specific to Galaxy Tab 3 10.1. Same app runs significantly faster on a much older beat up Samsung Galaxy Note 2.
Other folks are running into the same issue. (http://forums.adobe.com/message/5773513) . This device ships with an Intel based chip. Air is not supported on Intel x86 based Androids (atleast from their tech specs) http://www.adobe.com/products/air/tech-specs.html
===============
Android
ARMv7 processor with vector FPU, minimum 550MHz, OpenGL ES 2.0, H.264 and AAC HW decoders
Android™ 2.3 and above
256MB of RAM
===============
Really not sure what other folks are doing to combat this, The galaxy tab is probably going to be among the most popular Android devices this holiday season. Does anyone have a similar experience?
When an AIR app is exported to iOS, it is compiled to native code. The Android version is compiled to the AVM bytecodes and is interpreted. This is probably the difference in performance.
I know there have been some requests to compile AIR apps to native Android code, no idea what plans are in place for this.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am doing some research on SmartTV development right now and the topic seems very very fragmented.
I mean:
If you want to develop a android app, you get eclipse and the android sdk.
If you want to develop for iphone, you get xcode.
But SmartTV?
There is a Samsung SDK, a LG SDK, Google TV, a SmartTV Alliance SDK...
So what should I choose?
Especially if i want to
write once, run everywhere
enjoy mature development environment and tools
If you want to write once... you should choose the "The App Engine" but it's not free, it costs 48.000$/year with a max of 8 apps developed.
The second option is the SmartTV Alliance SDK.
The most mature SDK is the Samsung one, the LG one is good too but support from the manufacturer is not so good.
HTML is surely the best promising technology but we should consider that the market is very fragmented now. The first manufacturer/platform that obtains an important role will own the entire (and growing) market.
Actually the best options (in my opinion) are:
- PlayJam: they have a big experience and they're the most advanced platform today, they're partnering Steam too
- Google TV: it could become the Android of TVs... indeed, it's an Android-powered OS and LG, Samsung, Sony and Vizio already have a GoogleTV-device, Philips will add itself soon to the list.
So far the only two options are Adobe AIR and HTML, what do you have to develop?
We're developing some casual games and we use Adobe AIR
http://www.youtube.com/watch?v=0e8cmy1Vmic
http://www.noriste.com/lg-smarttvs-adobe-air-3-0-and-app-test/
Some (maybe obvious) links:
Samsung SDK - supports Java, HTML, Adobe AIR - samsungdforum.com
LG SDK - supports HTML, Adobe AIR, Unity - developer.lgappstv.com
Google TV SDK - supports Java, HTML, Adobe AIR, Unity - developers.google.com/tv/android
SmartTV Alliance SDK (LG, Sharp, Philips) - supports HTML - smarttv-alliance.org
NetTV SDK (Sharp, Philips) - supports HTML - yourappontv.com
Roku SDK - supports C++, Unity - roku.com/developer
PlayJam SDK - supports Adobe AIR, runs on LG and Samsung (they'll support HTML) - playjam.com
TV App Engine - supports HTML and converts apps into native ones - tvappagency.com
Marmalade - supports C/C++ and integrates the PlayJam APIs - madewithmarmalade.com
Yahoo Connected TV - supports HTML - connectedtv.yahoo.com/developer
Opera TV - supports HTML - dev.opera.com/tv
We are developing cross-plaform. It is all about the experience. Once you finish 2 or 3 applications you are aware about the differences between Samsung, LG, Sony, Philips and Panasonic and you can work with that. Of course the QA process and testing on TVs is different chapter - we have 30 TVs for testing only.
On the other side we have 30 Android phones as well, so comparing Android and SmartTV fragmentation I do not see that big differences, same situation was on Symbian, similar issues you have across different web browser versions or even iOS versions.
It is nothing that should scary or stop you.
BR
Petr
www.mautilus.com/blog
Try BBC Tal frame work, its open source and supports most of the smart tv
http://fmtvp.github.io/tal/getting-started/introducing-tal.html
Building Android TV Apps
Android offers a rich user experience that's optimized for apps running on large screen devices, such as high-definition televisions. Apps on TV offer new opportunities to delight your users from the comfort of their couch. More...
Dependencies and Prerequisites
Android 5.0 (API level 21) or higher
Android Studio 0.8 or later and Gradle 0.12 or later
Building Apps for TV more detail here..
Does anyone knows how to implement Sencha Touch with Nokia phones, Symbian operating system. As far as i make research i saw that it is possible to implement, there is a video with N8 implementation: http://www.youtube.com/watch?v=ERwS1sBRY-w
Thanks.
Sencha Touch is not officially supported on Symbian Devices.
Sencha Touch is a cross-platform framework aimed at next generation, touch enabled, devices. It's currently compatible with Apple iOS 3+, Android 2.1+, and BlackBerry 6+ devices. Together these devices represent over 95% of current US mobile traffic.
As the video shows it may still be possible to point the Nokia web browser to a Sencha Touch mobile site and have it work properly. The Youtube comments link to a git project that has a sample native Nokia app to get you started building Sencha Touch projects for Nokia. Something like PhoneGap may help you in deploying to Symbian devices.