<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Android app terminated</title><link>https://sourceforge.net/p/multimandel/wiki/Android%2520app%2520terminated/</link><description>Recent changes to Android app terminated</description><atom:link href="https://sourceforge.net/p/multimandel/wiki/Android%20app%20terminated/feed" rel="self"/><language>en</language><lastBuildDate>Wed, 30 Oct 2013 17:41:38 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/multimandel/wiki/Android%20app%20terminated/feed" rel="self" type="application/rss+xml"/><item><title>Android app terminated modified by Arnold Reinders</title><link>https://sourceforge.net/p/multimandel/wiki/Android%2520app%2520terminated/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;For termination the usual suspects (OnClose, OnDeActicate, OnDestroy, Destroy) don't fire. See &lt;a class="" href="http://stackoverflow.com/questions/19626892/how-to-detect-the-termination-of-a-program-in-android/19627007#19627007" rel="nofollow"&gt;this article&lt;/a&gt; for the workaround. Anyhow, this sparked a discussion in our team whether one should react on the termination of an application on mobile platforms. In general mobile apps don't die, they just fase away. That means a radical different approach. One should be aware that an application might be terminated any moment. Results that should be saved over terminations and restarts should be saved at logical moments, for example when values change.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Arnold Reinders</dc:creator><pubDate>Wed, 30 Oct 2013 17:41:38 -0000</pubDate><guid>https://sourceforge.net041586a50f6933c8b258b239c704b03d434261c9</guid></item></channel></rss>