I am developing an Android (and iOS) application for a client. The app is installed on devices with AirWatch, and I need to be able to read AppConfig parameters set by the AirWatch console.
I was able to do this on the iOS - quite simple. But not on Android.
Anyone knows how this is done?
Can you point me to sample code/tutorial/documentation?
See https://www.appconfig.org/android/ and https://developer.android.com/work/managed-configurations.html.
Implementation in Android is harder than on iOS, and the restrictions must be validated by updating the app on Google Play Store (or Android for work private store).
Related
If I build an app for iOS and Android and I distribute it. Let's call this the basic version of my app. A year later, if I decide on a change to my app (a new view or feature) but I only want to distribute this to some users, can I list it as a separate app on the app stores as a "extension"? Then when downloaded (by someone who already has the basic app) it simply extends the functionality. If it's downloaded by someone who doesn't have the basic app, it prompts them to download the basic app along with it?
Yes, you certainly can do this. Android platform offers IPC (Interprocess Communication) mechanism via AIDL (in Android every app is run in its own process by default) and it will be probably used to communicate between your apps. To get information about other apps you can use PackageManager.
My web application run's nicely on every smartphone. An additional native iOS/Android app would have the advantage of being available over the app stores and more visible to users. But I find it unnecessary work to do everything from scratch in all the development environments.
Instead I could make an app that just implements a web browser and just shows the website. Does someone know if this is allowed by Apple/Google at all? I have heard that at least Microsoft seems to have nothing against it in their Windows Phone market.
Thanks
# quape, apple will reject the application made with the idea you are thinking so it will be of no use to move in this direction.
Apple will simply reject the application for lack of functionality...
I have absolutely no idea about Google's policy on that question.
Here's the case:
I'm building an app and distributing it for beta-testers through Testflightapp.com.
Testflight provides a useful SDK, from which you can detect the user's interactions in the app.
The problem is, that although I've implemented the SDK as every tutorial/guide/forum-thread says, I'm not recieving any data..
Here's the data from the file running the testflight sdk. I've tried both the com.0x82.testflight-sdk-module from Titanium's own module-site and the NappTestflight-module (https://github.com/viezel/NappTestFlight).
What am I doing wrong?
(I've tried changing the guid of the app to the app-token and running it with normal guid)
Thanks !
I use this module to talk with TestFlight.
Setup was simple, and it is free. You need to check inside your App on TestFLight to get the correct id.
I have an application built with PhoneGap, and I want to send it to my clients with an elegant interface and get feedback. I have used testflight before for iOS, but it is not available for Android or BlackBerry.
I installed HockeyKit on my server. The alpha version of HockeyKit supports Android but there are a lot of files to upload and organize.
Is there any solution that can handle all three platforms - iOS, Android and BlackBerry?
AppBlade supports all three of the platforms you are looking for. To be honest I have only used them for Android, but it worked pretty well for that. I also got some great support from their engineers when I had questions and they also seemed to be fairly responsive to feature requests.
Knappsack sounds like it might fit the bill. It's a mobile application management platform that allows over the air installation of your apps and fine grained control of the users that have access to said apps. It's open source, so you can install it on your own server, but there is also a free tier that may suit your needs.
Can try HockeyApp, but it does not work with Blackberry. It is the best analog testflight.
It's early 2015 now and the solutions listed above either don't exist any more, or aren't free if you have more than a few apps/testers.
The best TestFlightApp.com alternative that I have found is Crashlytics. They support iOS and Android (no Blackberry).
Here's some info on the service: http://www.crashlytics.com/blog/launching-beta-by-crashlytics/
And here you can sign up: http://try.crashlytics.com/beta/
My customers prefer it to TestFlight, and for me as a developer it's also easier because they have an OS X app through which I can upload the archives and invite new testers (TestFlight's desktop app was broken for me).
Another really nice feature that Crashlytics offers is that (if you enable this feature), the OS X app will automatically upload the symbol files. When the app crashes for your testers, you'll get an email (when it's a new issue) and you can view statistics and stack traces of the crashes that occurred.
I am looking into building an android app, which holds some simple data (probably stored in sqlite). I also have a app engine app which I intend to be an online data store for the information (the app engine app is wrote in python).
The question here is, what is the best way to authenticate a user with the app and how to get the data from the android app to the Google data store?
Thanks
Mike
You could use Google Account authentication and follow this useful post about Authenticating against App Engine from an Android app
You can also give a look at the SampleSyncAdapter sample from the SDK
If you want to authenticate using OAuth, you can do that. The only trick is that you need to launch the flow in an internal WebView, because App Engine's OAuth implementation doesn't allow custom protocols in the redirect. I recommend the Signpost library. If you'd like an example, the 2cloud Android client is licensed under the MIT license (full disclosure, I'm the lead dev for 2cloud). The benefit of this is it allows you to support Android 1.5 and higher. The Accounts API is only supported starting in 2.1.
Another option is the Accounts API. #systempuntoout has good links for that, so I won't reinvent the wheel here.
Finally, it might be worth taking a look at the App Engine-powered Android Eclipse project that was demo'd at I/O this year. It makes keeping code in sync and shared between the two simple. Only downsides are it requires Android 2.2 or higher, and it requires you to write in Java on the App Engine side and GWT for the client side.