Has Adobe won the mobile war? I think so…

There is so much misinformation out there it is ridiculous. I hear so many rumors from non-developers about mobile development and the funny thing is, most of them have never developed an app. So why has Adobe won? Two software packages – Adobe Air and PhoneGap.

Each of these software packages allows you to create mobile apps on multiple devices. So I can develop one app and it will run on the iPhone, iPad, and Android based devices. Thus I no longer need to waste valuable time developing apps for both iOS and Android when I can develop one that deploys on both.

With Adobe Air, you develop your app in Flash and package it for each device. Wait, isnt there a rumor that Flash doesnt work on iPhone? Yes there is that rumor and it is only partially true. Flash does not run in the iOS browser BUT it will run as a stand alone app. So YES you can develop apps in Flash for Apple and they work very well.

With PhoneGap, also owned by Adobe, you can develop apps via HTML5 and then publish to Android and iOS devices. Again these work very well.

Additionally, with both of these software packages I can actually use hardware features of the phone and use them when not connected to the internet. Something you can do with all mobile apps but not the mobile web. The disadvantage to developing an app over a website is that Apple has to approve it (not a problem with Android). Otherwise Apps are much better than a mobile website.

Why would I use one over the other? Flash apps are designed for more sophisticated apps that require large amounts of data (database), high intensity graphics, lots of screens, animations, etc. PhoneGap apps are better for small simple apps. Both are great for development though. Additionally, Adobe is really starting to integrate phonegap into dreamweaver so I would not be surprised if we see these two software packages merged at some point (maybe CS7?).

I will be using both of these software packages in my courses next year, so if you are interested in learning more about them, please contact me.

Adobe Air – http://www.adobe.com/products/air.html

PhoneGap – http://phonegap.com/

Two of my Android Apps now available in Android Market Place (Play)

Here are two Android Apps I created that are now available on the Google Market Place (Google Play). They are both free and both display surf reports for the states of NJ and NC. I created these apps in Eclipse using Java. They are the first apps I have created using Java. I actually believe it might have been just as much work as using the Google App Inventor. I will now be creating all of my apps via Java from now on and doing some more advanced stuff in the future as I have time.

North Carolina Surf Reports App

New Jersey Surf Reports App

iPhone vs. Galaxy Nexus vs. S3? Can’t compare on specs alone

While certain features of these phones are comparable, like the camera. There are just certain things that you cannot compare when looking at these devices.

For instance, while the 1.2 dual core processor or 1.4 quad core processor seem to blow Apple’s .800 dual core processor out of the water, this couldnt be further from the truth. Many forget that Apple runs a different OS. Meaning that Apple’s iPhone is built specifically for their OS. They didnt need a 1.5 quad core processor because their OS does not require or utilize it. Additionally, you cant really even compare the Gnex to the S3 for the same reason. While they both run ICS, the Gnex runs a vanilla version of the OS and was made to specifically to run the OS just as the iPhone was for iOS. The S3 contains TouchWiz, which is Samsung’s bloatware and thus needs that extra power that the Gnex does not need.

All in all, there are some things you can compare but overall you cannot compare these devices by just looking at the specs. The specs are not very helpful in really telling you much about the big picture, they are simply a small piece. Each of these phones is so different that it’s going to be a matter of preference which is better, not the one that has the best specs is king.

New Samsung Phone: Galaxy S3

For more info: http://www.thenextgalaxy.com/

Galaxy S3 confirmed

– 4.8 inch screen
– 8mp camera (1.9 inch front camera)
– 2100 battery
– summer launch in America
– looks very similar to nexus
– 2 feature – s-voice and s-stay – both look ok but are bloatware.
– 1.4 GHZ Quad core processor
– MicroSD slot
– Runs ICS Android 4.0
– 1 GB Ram

My thoughts from what I have seen ( I have not touched the phone or seen it in real life): It’s a definite upgrade the S2 and GNex, however, it is not what I would call significant. It’s reminds me of the upgrade from the iPhone 4 to the 4s. Some specs are great, like the quad core, and microSD card. But the S2 has an 8MP camera already. And while Samsung is really pushing their bloatware – it’s bloatware, although I will admit that if you did not want the bloatware you already have a Gnex which has a vanilla version of Android 4.0 on it. Would I buy this phone? Well I have the Gnex so there is no way this is worth the upgrade. I personally do NOT want bloatware – but that is my big selling point. Additionally, I have the extended battery for the Gnex which is the same one used as default on this phone. Others really like the microSD card, that alone may be a huge selling point. If I had the S2 I would probably upgrade although honestly if you care about a better camera, phones will have 10-12mp by the end of the year.

Samsung Galaxy S3 to be announced tomorrow (May 3rd)

For those that have been waiting for this phone tomorrow is the big announcement from London: 2pm EST

Here is the website and access to live streaming from the event: http://www.thenextgalaxy.com/

Current phone rumors:

– quad core 1.2 or 1.5 Ghz processor
– 1 GB Ram
– 12 mp camera
– 720 or 1080 screen
– Android 4.0
– all carriers potentially

Here is a video with the add:

When to design for the mobile device

The following blog post will discuss when you should consider developing instruction for the mobile device. Developing for the mobile device presents several challenges that differ from the PC. Currently, there are not many best design practices recommended in the research, usability is different, and compatibility is a major problem. However, this post will not discuss those issues, I will do so in others posts but instead will focus on when to consider mobile learning in your training solution. Why are we currently developing for the mobile device? Well in some cases we are just doing it for the sake of doing it, not when it is actually warranted as noted by our instructional analysis. The reason I bring this up is because mobile learning is a ‘hot’ topic right now. However, the best uses for mobile delivery are only a very small portion of training but many are trying to use it for all training solutions.

Before developing instruction for the mobile device, I recommend making sure that mobile delivery of the instruction fits into your instructional objectives and strategies. Are you trying to develop for the mobile device so that employees have a option to view this on their iPad or mobile phone? If so, I would develop for the PC. Most instruction that is meant to be viewed on the PC cannot be repackaged for the mobile phone because the instructional objectives just are not meant to be delivered in that medium due to the significant differences in screen size, usability, design options, time for delivery, etc. The mobile device is NOT meant to deliver the same training that the PC can. If you are trying to develop training for both, and both have the same objectives/strategies – then you are cutting corners somewhere and sacrificing quality. They are both used for different reasons and it is these reasons, which are identified in your front end analysis, that mobile based instruction should be considered.

I would develop for the mobile device when employing instruction that is real time – i.e., happening while on the job or on the go. For instance, it is a great way of delivering job aids and real time how to’s.  It is also great for delivering training that is mobile, such as training in remote areas (with no wifi) or training solutions that require being on the go. An example would be a child at the zoo – where each animal would reveal information about the animal. A laptop or PC would not be convenient to carry around but a mobile device would work well with this type of instruction. Another example could be a soldier out in the field who needs to learn how to perform a task that they might not be skilled in but needs an immediate solution. It is here that mobile delivery shines. However, normal 1 hr computer based instruction will not shine on the mobile device – it is meant to be viewed on the PC. So you really need to ask yourself: What device makes the most sense for this instruction? If it’s mobile, then develop for mobile; if PC, then develop for PC. However remember that objectives/strategies for each medium will be different and if you are developing using the same objectives/strategies for both you are cutting corners and sacrificing quality.