I need some reference of device cloud provider where i can test my native mobile app developed. I have already found on one appthwack but was wondering if there are any better options.
Thanks.
Testdroid - http://www.testdroid.com/ - over 400 Android and iOS devices, some for free.
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 am working on an iOS app which need to get push notifications(using GCM) from web service(Made of Python).
Currently the web service works fine with Android devices, but it reports Error=MismatchSenderId, when I check this error in the online doc, it suggests the sender_id and API_key are not matched. The thing is, as I understand it(could be wrong), for iOS SDK, unlike the Android's, it doesn't need sender_id.
The tricky part is I have no access to the web service yet(which the collaboration party claim the Android app works fine with it). Could anyone shred a light on what steps should I take to fix this issue?
THanks in advance.
since I am new in the world of developing apps for watches, and the fact that it exists for smartphones the following frameworks:
Xamarin
PhoneGap
appcelerator
kony
Cordova
...
I wonder if there exists for watches apps similar frameworks? So that you code once but run overall.
Thanks
Edit 1:
At this day (12.05.2015) regarding to the answer of a nativescript maintainer here. I will go with nativescript to start writing app for wearables.
Cordova/PhoneGap apps don't work directly on the wearable devices/watches. Cordova/PhoneGap is basically a javascript API which can run on WebKit/WebView on all the mobile OS's. But the Android Watch and Apple Watch doesn't support WebKit and so the apps developed with Cordova don't work directly on Watch devices. But if want to extend some of the features from the existing Cordova app to the wearable app, you need to create the extension app in native language and the extension should be able to communicate with the paired app on the mobile device. The extension on the Watch will have only UI and the bussiness logic etc runs on the Cordova app on the mobile. It is possible to establish communication between these apps which will drive the display on the watch devices.
I am not sure about the other frameworks you listed above on how much they support wearable devices.
As #kiran and #NRimer have mentioned, these cross platform frameworks are relying on the WebKit/WebView which is the almost universal layer supported on every mobile device. They dont run directly on the device, but device runs WebKit platform that runs these cross platform apps. So comparing the capabilities of the native app with cross platform app, native app is bigger, because it can have a hands on device hardware related features. The thing particular to the smart watches is that they mostly rely on other smart phone device, and it uses it's communication protocols, that are hardware specific, and WebKit doesnt have its hands on it.
It depends on what you're looking to do with the framework. Watch apps build off data provided by their containing app. For example if you want to provide custom notifications on the watch, the app (or server for remote notifications) constructs them. When your watch app needs information, it makes a request to the containing app. Lets say you have a group of apps that you want to provide the same notifications or functions on each of their watch apps, you could make a framework that handles these functions for the containing app. As for the watch portion, think of it as more of a display of information provided. Unfortunately i dont think there's a way to generate frameworks for watch apps yet. If you're looking to have a lot of code within the watch app this might be more difficult but for simple display of information you should be alright.
Market has added device compatibility check.Now we can check if an app will work on specific device, for exaple HTC mobile phone, Samsung Galaxy, etc.
What about developer's side: How can we build apps for specific devices only or restrict app for tablets only? How to do restriction in XML and code? It's probably some attribute in Manifest file.
Thanks
Here "Specifying Your Application's System API Requirements" ?
It seems that Market checks this out by itself.
My web app is written in Java with front-end in JS. I want to port to tablet and other touch mobile devices. Developing a native API is ofcourse an option but I would prefer making the old app work on tablet.
I know I would need to make some changes in UI for the touch interface and I am willing to do it.
So My question is: A*re there tablet Simulators available on which I can try my app and see where it breaks on such device.*
What would be the best approach to proceed on this?
thanks in advance!
Tablets use various OS's and, thus, different API's, supported features, etc... For iPad, for imstance, XCode provides a simulator. I read somewhere that the BB tablet coming out will have a simulator for dev as well.