Hi everyone am new to android and developed projects on c, dot net frameworks and python. I have to develop application for android and iPhone tablets. Currently I have to write application for android and have two options.
1) Use java and android sdk
2) Use Phonegap
I would love to use Phone-gap because it's seems pretty much easy as I am familiar with HTML, CSS and JavaScript. But that's not my limitation as I have used jav with E-clips earlier. much better hint is single app for android and Iphone.
My question is if phone-gap will work for me. what I need to start my app on start-up without showing desktop and always on top. and read screen on/off actions. I have crafted kiosk and installed 10.1" android 4.1 tablet. I have to develop app to give it a POS look. My app should start as early as my device boot and always remain on TOP unless explicitly closed.
Any suggestion will be helpful for me as I am new and have only created hello world app on both.
Related
Is it possible to use Android Things on a tablet?
My project needs Android Things, but I can't use Raspberry for it, because it will be expensive.
If not, what do I do to a "normal" Android (Android for tablets/phones) to have only my application, don't have notification bar and don't close my app with the life cycle? (like on Android Things)
It's possible to use Android things on a tablet?
No. Here is the list of supported platforms.
If not, what do I do to the "normal Android".
Develop a kiosk mode app or, if it's not enough for you, customize Android source code.
I am wondering if it is possible to run an tizen wearable app in background. I need to run an app in background. I am using several sensors and I need to save these data continuously.
another thing Can we get the sensor in Samsung Gear S2 data such as Heart Rate directly from an android app directly without any widget on the Gear S2.
I appreciate any help or suggestion.
Thanks,
I'm also new on this and I'm starting with Samsung Gear S2.
When I read your post, I thought I read somewhere that Gear S2 would only run web app, yet, I opened the Tizen IDE, used a sample native app, and installed it an ran on Gear S2, so, I would say that you probably can do it. I would just explore the native sample apps for start, you'll have to develop in c/c++ and as you might know, you'll need to instal the Tizen IDE and the Samsung Extension SDK (http://developer.samsung.com/technical-doc/view.do?v=T000000248)
hope it helps.
It wasn't possible in the first Tizen version that supported wearable (2.2) but became possible later (2.3) when native and hybrid apps were added to the wearable profile.
Not sure how running Android apps on Tizen is really implemented, but I'd expect the chances of Anrdoid apps getting access to device information (sensor and other) is fairly unlikely, as those come through Tizen-specific APIs with also Tizen-specific privilege requirements - the mapping would be complex, but who knows, someone may have managed it. You don't need a widget for that though, the same device information API (and more) is available through native apps.
Yes it is possible to create wearable background app but only with Tizen 2.3 & above and only in Native app versions not in Web apps.
If you want to build app in web version then u can write your service in native and UI in web app and make the app as hybrid app.
Follow the guide in link below to pack a hybrid app:
Tizen Hybrid App Packaging guide
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.
We need to create an app, which works for time tracking of the employees as well as location tracking.
We only want to program it for Android, but we don't have any Android skills.
Therefore phonegap came as a great alternative.
But there are several questions, to which I can't find a clear answer in the web.
If the phone is in standby mode, can the phonegap-app still send position data? Would this still be phonegap standard or do I need to use plugins?
the smartphones will be very simple and cheap. Is there a higher risk, that the phonegap application gets closed by Android to free memory then for a native app?
Alltogether, could it be recommend to invest the time to learn Android or would it be better to stay at our language JS?
It’s perfectly feasible to write a location tracking application using phonegap and have it a) work in a performant manner on low spec android phones and b) keep the app running in the background when the phone is in standby mode.
To keep the app running in the background on android, it’s necessary to acquire a partial wakelock (see android powermanager). In phonegap, you need to use a plugin to achieve this. On the plus side, there’s an existing phonegap plugin to do this. The downside is that in order to use a custom plugin, you will not be able to use the convenient phonegap build method to build your app, so will need to do the manual process via the Eclipse IDE, but this is not a great hassle to set up (see here).
In terms of your app getting closed because of android running out of memory, and also having it perform responsively on cheap, low spec devices, this won’t be a problem so long as you are careful to write your javascript code in an optimal way. I’ve implemented a location tracking app using phonegap which uses custom maps and in testing on older android devices including HTC Desire and HTC Wildfire, performance was acceptable and the partial wakelock worked - I had no problems with the app getting closed because of lack of memory.
I chose phonegap over native because I’m a web developer so Javascript is more convenient for me than having to start from scratch with Java and the android SDK, and also because I was able to use the same JS code base with appropriate plugins to produce the same app for iOS. Phonegap is able to access GPS hardware on the device and in testing outside I found the average accuracy to be between 4 to 8 metres depending on the device.
Hope this helps!
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!