I am working on a project where I am developing mobile app (android) using react native. The development of the app is fine. However, I need to remove all other apps from the existing device (I am using Nexus 7) but except settings and my app (the one that I am developing).
This special requirements is a must have as the device will be giving to the customer for one purpose only. So I need to have only one app installed and disable any option to installed any other apps from the app store.
But I have no idea, how I might be able to do so. So I really need your help. If you could guide me on this, would mean the world to me.
AFAIK you can't remove the standard applications because they are stored in flash memory (OS image) and this memory is readonly. What you can do is to download entire android, build own image stripping all the unnecessary services, applications, etc. And then flash this new image to the device. The process is not sample and straight.
Related
I've been developing a mobile app for both iOS and Android. Due to time/budget constraints, we initially selected PhoneGap/Cordova as mobile app framework so we could write once and deploy to both platforms.
This plan has worked fine for iOS, but we're finding that Android's browser/engine is kind-of a piece of garbage (to put it nicely). Every time we add a new feature, we find one more thing that the Android browser doesn't support, or only partially supports, or fully supports but will randomly fail from time to time, etc. Even once we code around the Android issues and get things working smoothly, test it on multiple devices/versions, and deploy a new app to the Android market, we immediately start getting emails and reports from customers who can't get the app to work on their device. We have them uninstall/reinstall, reboot their phone to clear the memory, etc., and their device still consistently fails (and by "fail", I mean it typically just freezes and/or won't respond to touch input - it usually doesn't crash, or anything). The app works fine for most people, but there are still quite a few devices that inexplicably fail.
I don't mean for this to be a rant, I'm trying to analyze whether the Android+PhoneGap path is the correct path for us. Specifically, I'd like to find out the following:
Are there people out there having success with an Android+PhoneGap app? or is Android+PhoneGap always going to be a problem on certain devices?
Am I likely to have more luck with a native Android app (I've never attempted one)? Or are multiple devices/versions always a problem on Android, even with a Native app?
1) Yes. There are are good apps which are based on Phonegap and works well in all devices.
2) It depends on what features of the Android you are going to use. Few versions that does not support some features that's available only to new version.
BTW, what is the minimum required version that you have selected for your app? I assume you are developing the app with Android as base version.
When creating a new Android project, you have to set the minimum required platform version. If you set something higher and use the app in a lower version which does not support the feature, results are going to be different.
After having worked with Android+Cordova for some time now, I have the following suggestions/comments for anyone thinking of going that direction.
Consider using Sencha Touch, or jQuery Mobile, or another mobile framework that has already coded around the Android-browser issues (which there are a LOT of). Consider not straying too far from the default styling that come with those frameworks. Simply styling a normal web page to look like a mobile app is a constant headache to get working on multiple versions of the stock Android browser.
Although the stock Android browser is garbage, Mobile Chrome is pretty nice. In Android 4.4, the Chrome engine becomes the default engine used by a webview of an Android app. If you don't like Sencha or jQuery Mobile or the like, you could hold off and just use a mobile web site for a while until Android 4.3 and below become insignificant. It's not hard to get things working on Mobile Chrome.
Even without Sencha/JQM, you can still muscle your way around the stock browser issues, but it's almost as frustrating as developing for IE6. Okay, maybe not that bad… but close.
I've started experimenting some with a native Android app, and, so far, it seems like less of a headache than building an app with Android+Cordova+lackOfSenchaOrJQMorTheLike. The things I've experimented with work pretty consistently among different Android versions. But I don't have much experience there, so I can't comment too much on a native Android app.
I want to Ask One Question that is More Important For Android & IOS.
We see in IOS You Can Run IOS App (Created By IOS Phone only) that app Run in Tablet
Device & work As Iphone As shown in Image.
Is there Any Way to Run Android App (Created By Android Phone only) that app Run in Tablet Device & work As Android Phone As shown in image.
is this Possible in Android!
Any help?.
Android actually handles this better than iOS, it scales the app up. Any app on the Play store which isn't being filtered will work on any Android device.
In iOS you have different views for your iPad/iPhone on Android you use Fragments to acheive the same result see Designing for Handset and Tablet.
Personally its better on Android as you can reuse componentized UI.
IF you really want to make it look like a phone app, you can use scaled mode, (if you target your app against gingerbread targetSdk="10") then Honeycomb+ will present the users with scaled mode similar to the iOS thing. I by no means recommend this! It is the worst UX you can give your users!
I just started to learn how to program an Android applications. Coming from a C# world, one thing that bothers me greatly about Android programming is the fact that it takes forever to actually test your app because you have to fire up AVD or wait until the app is installed on your actual device whereas for Winforms/WPF applications, you just hit that debug button and everything loads within split seconds.
My first question is, which is a more preferred way of developing to maximize efficiency? Develop on AVD or an actual device? Are there any suggestions on how I can improve my development speed?
A few things, most people leave the AVD open whilst they are developing so that they don't have to wait ten minuets every time they open it, however if you have a very slow computer and this is not an option then yes it will talk a while
If you have a faster computer then AVD is likely to be less laggy, but for a completely lag free testing place, use your actual device.
If you are making games you should look into libgdx because it allows you to test your apps on your desktop, then by changing one line, export them as .apk files and test on you android device
For a lot of apps and features within apps you will be left with no option but to test on your real device. Because it can take a while moving the .apk file to the actual device, I would recommend using an on device IDE to make small edits to your code whilst testing certain hardware features such as the volume buttons or the accelerometer. As for on device IDEs I would recommend AIDE - https://play.google.com/store/apps/details?id=com.aide.ui&hl=en
On the whole, I would recommend using eclipse with AVD, for the majority of your development on the majority of your apps, but for any apps that you need hardware functions for, I would recommend using an on device IDE (search the play store for android development for more options if you don't like my recommendation). Most importantly don't list your app until you have tested it on multiple screen sizes on the AVD, and you have tested it on you physical device
Keep the AVD open, you can keep doing debugs and test on it, it will automatically close and reopen with new code, that’s how I do at least, and I am the same, came from C# no experience with Android.
I have an Adobe AIR desktop application, built in Flex Builder 3, that I want to run on an android device, specifically a Samsung Galaxy Tablet. I have put the application on an emulator, going through the steps of installing AIR on the emulator, packaging the application as an APK, and installing the application on the emulator. However, when I click the application, it does not run.
Here is my question: is this even possible? Can a desktop application be run on a mobile device with no changes to the code, or does it need to be converted to a mobile application before compiling? Thanks for any and all input,
T
So the answer is yes you can deploy that to a mobile device. As far as changes to the code is concerned, the answer is it depends. If it's a simple application, you shouldn't have to change anything.
Since there is no way (from what I understand) to create .apk files in Flex Builder 3, I am assuming you are going through the ADT command line to package it?
And you are following all the steps on
http://help.adobe.com/en_US/air/build/WSfffb011ac560372f-5d0f4f25128cc9cd0cb-7ffb.html
Once we have that covered, other questions would be: Are you using any modules or a framework? Any error messages?
From what I understand, Android doesn't support mx components, so depending on what you are doing there, yes you might have to change the code in order to make it work for Android.
Hopefully that helps.
Is it possible in Android, to disable standard features of the phone such as Mail, browser, phone etc?
What I'm asking is, is it possible to create an application that, when launched on startup provides some features to the user, but sits "on top" of android so they only have access to your application and not the underlying features of android itself?
Effectively, the phone still runs android, but the user never gets to see this as they are limited to the functionality that your app provides.
You can replace all of the stock apps that come in the AOSP. browser, dialer, homescreen, etc are all just APK files you could replace them with any other APK file you want, lots of ROMS from the Android mod scene replace the stock apps for more robust versions.