Tag Archives: Mobile Programming

New Smartphone App for My Little Sister

My little sister and I were on the phone, and while were talking, the phone gets disconnected.  I wished her a Happy Birthday,  then started spouting technical stuff before we were cut off.  So I thought of a cool app for dating.  If the API is opened up for voice recognition, you are able to make a host of applications.  One of the apps may allow you to enter a list of words that you find boring in a conversation, e.g. Quantum Physics, and if the app running in the background detects one or more of these words on the list, it could play an mp3 file with static and disconnect the call.  So all the people dating, if you give someone your number at a bar that does happen to ‘call you’ and they are boring to you, the application intervenes in a old, yet politically correct way.  Just a bit of of plausible humor.  P.S. Don’t create a similar application for Who Wants to Be a Millionaire, which searches the Internet, and prompts the correct answer, that’s cheating!

Mobile Memory Management Advantage: Multithreading in Android verse Apple iOS

I walked into an electronics store today in Athens where they proudly displayed the latest Mobile technology like the iPads (iOS), Android and Windows OS tablets, and as you enter the store, I believe roughly in that order. However they had iOS in front of the store, but MSFT translation terminals for inventory, transaction execution, etc., which is interesting politics, in itself.

Anyway, as I was leaving the store, collecting my US power converter, I noticed something I’ve seen dozens of times before especially in previous iOS versions, but the latest iOS still has its multithreading implementation with applications exiting to the main menu, but not quitting, therefore leaving a memory footprint, and the application at the very least, is in a low memory, idle CPU, and at the most, a potential for issues with consumption of the resources mentioned.  I’d suspect the application is still running in memory for notifications.

To the contrary, in the Android OS, you will typically have a quit application menu option; however, I don’t remember how they perform the notification process, think it runs as a separate thread, as a service, not Y application, which one may argue may take up more memory.  However not all applications are designed to provide notifications to the user, therefore not a one to one correlation of Android application to a service.  Apple iOS forces a memory footprint regardless. Inefficient resource management on a relatively resource constrained device.