- Google app engine sdk eclipse helios puglin update#
- Google app engine sdk eclipse helios puglin android#
- Google app engine sdk eclipse helios puglin code#
- Google app engine sdk eclipse helios puglin windows#
Users generally don't need anything else, for properly-written applications, any more than they need a "quit" option for using Web applications.
Google app engine sdk eclipse helios puglin code#
iPhone is a bit different, in that it only presently allows one thing to run at a time (with a few exceptions), and so the act of leaving implies a fairly immediate termination of the app.Īs everybody else told you, users (via BACK) or your code (via finish()) can close up your currently-running activity. In all of those, users don't "terminate" anything - they just leave. Or WebOS, if I understand their model correctly (haven't had a chance to play with one yet). It finishes the activity that was on-screen when the user pressed the BACK button. Pressing the BACK button does not "kill the app". Either check updates on start or check updates totally asynchronously (e.g., via a scheduled task), never on exit.
Google app engine sdk eclipse helios puglin update#
For all you know, the reason your application is being "exited" is because the OS is shutting down, and then your update process will fail mid-stream. That is a mistake on any operating system. Usually, it is because they hold onto login credentials, rather than forcing users to log in every time manually.
Google app engine sdk eclipse helios puglin android#
There are many iPhone and Android applications that deal with this.
Use a scheduled task (via AlarmManager) to update your data for maximum reliability. I don't know what "lists with tasks that always should be there" means, but the "data being PUSHed to the device" is a pleasant fiction and should not be done by activity in any case. IPhone users are much the same way, in that pressing the iPhone button does not necessarily "feel" like the app was terminated since many iPhone apps pick up where the user left off, even if the app really was shut down (since iPhone only allows one third-party app at a time, at present). Those users simply don't think about "terminating" the Android app, any more than they think about "terminating" a Web page or "terminating" a thermostat. Millions of people are perfectly happy with the model where the environment closes up the application as needed. I have no intention of changing your mind - rather, these are here for others who come to read this post in the future. This will eventually get to your question, but I first want to address a number of issues you raise in your various comments to the various answers already given at the time of this writing. Is there a way for me to really quit the application? I hope I don't have to abandon Android, but it doesn't look very good right now =( However, the last week has been somewhat of a turnoff for me.
Google app engine sdk eclipse helios puglin windows#
I was actually really looking forward to developing for the Android platform, since it addresses a lot of issues that exist in Windows Mobile and. It is not an application for "wide use" by the general public, it is a business app that is going to be used in a very narrow business field. The application I am trying to create is not an application for the Android Market. That is not something that should be relied upon the OS to do. What's up with that? I am starting to think that it's impossible to write an app that functions as a "normal app" - that the user can quit the app when he/she decides to do so. Hehe, for every step I take in the Android world I run into some sort of problem =(Īpparently, you cannot quit an application in Android (but the Android system can very well totally destroy your app whenever it feels like it). This is also contrary to how core applications work. It is useless with Android's application model. No matter what you do, do not put a "quit" or "exit" application button. That's what the activity lifecycle (especially onPause/onStop/onDestroy) is for. How does the user terminate the application?Īnswer: (Romain Guy): The user doesn't, the system handles this automatically. Unless we put a menu option in to kill it? If no such option exists, Question: Does the user have a choice to kill the application Moving on in my attempt to learn Android, I just read the following:
0 kommentar(er)
