Reverse Engineering of Mobile Application Lifecycles

An Efficient Interruption Handling for 3D Games based on Android Platform

“…Therefore, we assume that an Android 3D game application uses unique Android Activity. Each Activity specifies the lifecycle as the Android Activity Lifecycle [2], [5]. The concepts of Android 3D game lifecycle and Activity lifecycle can be considered as identical.…”

“…1. Android Activity Lifecycle Model [2] An activity is changed to RUNNING state after returning from calling onResume(). Game users can interact with it as foreground screen.…”

“…While many applications in personal computer can run at the same time, in Android platform, other applications or events can interrupt current application [1], [2]. An unavoidable interruption event makes the game pause or stop and game users cannot interact with Game User Interface (Game UI) although it is visible, partially visible or not.…”

“…They help the game system catch and control interruption events by triggering them when interruption events happen. However, Android lifecycle methods are not always triggered correctly in all cases [2].…”

iOS Applications Testing

“…Other studies - [4] and [5] that include the clear distinction between the platforms, concentrate on some narrow topic. On the other side, there are different iOS testing checklists, mind maps, blogs etc.…”