Drill down to a product page on Walmart's iPhone app and they make it easy to consult your friends advice via Facebook.

Every mobile application targeting a retail or hospitality use case seems to have the obvious features: finding business locations, contact information, product/offering information, and in some cases user reviews/ratings of what’s being offered.  These apps amount in many ways to a repackaging of the merchant’s existing website as a native application for the iPhone or Android mobile device.  At the same time, there are also a number of interesting features that go beyond this basic “we gotta have an iPhone App too” mentality, and are beginning to utilize the mobile platform in new and interesting ways.  In what follows we highlight five such features that we’ve spotted recently in one or more free applications in the retail/hospitality space.
1. Integrate the experience with the customer’s social graph. You would think this would be obvious these days, given the rate at which major brands are staking out their outposts on the latest social media frontiers.  Yet, very few apps in this category integrate with the customer’s  existing social media channels.  GAP and  Walmart are two notable exceptions to this.  Once you’ve drilled down to a product detail page, Walmart’s iPhone app (dedicated to their consumer electronic offerings only) suggests you ask your friends on facebook (or via email) for advice.

GAP's StyleMixer App let's you beam a potential new outfit up on your FB wall to get reactions.

The GAP’s StyleMixer iPhone app goes a step futher in that you can dynamically configure an outfit (see next point) and then share it via GAP’s homegrown social community,  Facebook, and/or email addresses.

2. Assist in non-trivial product configuration/selection. Ever try to order pizza over the phone with a room full or car full of hungry adolescents all telling you their topping preferences at the same time?   Not to worry, Pizza Hut’s iPhone application is a well-executed example of using the mobile platform to quickly whip together a precise order with a lot of non-trivial detail.  There are other good examples of this same concept being used in retail to assist customers in product selection.  Both Target’s and BestBuy’s iPhone applications provide novel gift selection wizards that let you quickly select an appropriate gift for that hard to please mother-in-law. As we already mentioned above, GAP’s StyleMixer iPhone app let’s you assemble a new outfit, complete with accessories, and then share it with your friends via Facebook Connect.

Configuring and ordering your pizza is a snap using Pizza Hut's iPhone App.

3. In store positioning. This feature is not exactly widespread at least at the moment, due to the non-trivial nature of doing precise positioning indoors.  However, there are low tech ways that can be used to make the shopper’s life a lot easier.  Though not particularly well executed (latest update seems to have broken the app, at least on my phone) the “Point Inside” iPhone app is a good example of this approach.  The application provides floorplans of most of the larger malls within the USA.

Find your way around the mall with the Point Inside iPhone application.

Users can specify  where they want to go (by selecting the destination store from a list).  A Pin is then overlaid on the mall floor plans to help you gather your bearings and proceed to the store of interest.  The functionality actually goes well beyond the “you are here” directories physically situated throughout the mall in that in addition to finding stores and their contact info, it helps you remember where you parked your car, and/or quickly find that much needed restroom or ATM.  There are however, lots of ways to improve this particular app and make it truly useful for those of us who habitually lose our way in the shopping mall.

4.  Product interest/intent signaling. Making it dead simple for a user to quickly pull up information on a specific product/offer via a mobile phone is advantageous for the merchant as well as the customer.  One of the advantages online retailers like Amazon have is that they have a lot of information about the individual end user.  This information is at a very fine resolution and includes what products you’ve looked up, how long you spent staring at the product information between clicks, etc.  Traditional bricks and mortar retailers have little more than a list of past purchases to work with.  Using the mobile device as a sort of in-store concierge should provide better customer services (e.g. no need to find the guy with a blue shirt in Best Buy – just look up the reviews on your phone) and also help gather a lot of useful customer information beyond the end purchase decision.

The first generation of mobile applications supporting this sort of functionality have taken the obvious route – use the phone’s camera to get an image of the product’s UPC code and then access network services to pull down the relevant product metadata.  Two good examples of this are the Shop Savvy and RedLaser applications.  However, if you have any experience at all using a dedicated barcode scanning device you’ll find that imaging barcodes with a mobile phone is tedious and sometimes not possible in low light situation or when product packaging is such that there is glare on the UPC or its all crinkled up.  These apps have a backup plan of course, in that if all else fails you can type in the UPC code.

You'll need a steady hand, good lighting, and a phone with macro lens to get a good barcode scan with ShopSavvy.

What is shaping up to be an even more interesting  approach than scanning barcodes,  is that taken by Amazon in the “Amazon Remembers” feature in their iPhone app.  Here you simply take a picture of the product of interest and send it off to Amazon.  Amazon first attempts to recognize the product automatically, and if successful a response is sent back to the phone in literally seconds.  If Amazon’s automatic image processing doesn’t yield a it, hit gets outsourced to real human beings via Amazon’s Mechanical Turk and you’ll get product info in short order.

A more recent attempt at this approach is Google Goggles.  Goggles is intended to be a general “search by image” application and supports much more than product lookup.  Though somewhat limited in its current incarnation, it gives you a good glimpse of the future, where you really don’t need a barcode – just point your phone at any object (people included?) and bingo you have everything you want to know about it.

5. Information aggregation. One very common theme is that a lot of applications in this space are not provided by the brand or merchants themselves, but by a third party that is aggregating data from a number of sources.  The net effect is that the prospective customer is essentially armed with a real-time consumer guide in their pocket at all times.   If a merchant doesn’t give the customer the best deal possible, the app will tell them where they can get it, just down the road at a nearby competitor’s establishment or online.  Good examples of these sorts of apps are Shop Savvy (for retail) and UrbanSpoon and Yelp (for hospitality).  If these

"Amazon Remembers" utilizes a combination of automagic and human powered search to match a product to a user generated image.

sorts of apps aren’t already getting the retailers attention they soon will be as more and more people begin to upgrade to application capable mobile phones.  A good strategy for a retailer (beyond offering the lowest price and being as geographically ubiquitous as possible) is perhaps to offer a branded mobile experience of its own that provides a better experience than the third party aggregate apps, and possibly integrates more tightly with in-store experiences (indoor positioning, situated displays, POS, etc).

These are the best exemplars of these retail/hospitatlity mobile features that we’re aware of at the moment.  If you are aware of better examples, please do let us know.  We’re also interested in hearing from you if you can point us to mobile apps in the retail/hospitality space that incorporate features beyond the obvious, and which do not fit in one of the feature descriptions that in our list above.

Can't decide between the multiplicity of Thai choices in Allendale, MI? Give UrbanSpoon a shake and it will make the choice for you.

When I recently returned to my roots here at GVSU, I not only had to an assimilate an amazingly altered campus from what I left behind back in 1988, but I also had to get accustomed to the fact that GVSU now sprawls across the entire W. Michigan area. In addition to the main Allendale campus there is the gorgeous Pew Campus in downtown Grand Rapids, and a second downtown campus on “medical hill”, as well as campuses in Holland, and Muskegon.

Here on the main GVSU campus a project is underway to build a new library facility. This week a fly through of the new facility was published on YouTube. It is going to be a remarkable facility indeed! I was very pleased to see that among with all of the new ultra modern library technologies (including an Apple-like “Genius Bar”), the new library will still have a “Collections Wing” with a “Browsable Books” area where its patrons can wander among shelves of very real physical books and browse for good reads. Being the gadget geek I am, you all might be surprised to learn I don’t yet own a Kindle or equivalent dedicated reader device. I don’t know exactly what it is, but for me there is nothing digital that replaces the authentic experience of reading with a real dog eared tome in hand. Don’t get me wrong, I love Google books, and a Kindle is probably a much more practical form factor if you need to lug the equivalent of a box of books with you on a trip somewhere. However, to truly experience a good read, I still prefer the old fashioned media.

I’ve embedded the youtube video above.  You can read more about the new Mary Idema Pew Library Learning and Information Commons here.

Twitter now let's you organize your favorite tweeters into lists. A very handy way to add some order to the tweet chaos.

The new “list” feature on Twitter is fantastic!  Basically, twitter follow lists lets you the user organize your twitter friends into meaningful lists to share with others.  This morning I started organizing various lists relating to mobile technology that I thought would be of interest to others.  So far, I’ve put together the following lists:

• Mobile Manufacturers:  Every manufacturer of consumer mobile devices I am aware of that has an official and active twitter presence.  This includes their main corporate twitter accounts as well as specialized twitter accounts (e.g. mobile products business units, developer communities, etc.)
• Mobile Operators: Every mobile operator/service provider I am aware of that has an active twitter account.  At the moment this list has a North American bias to it.  Eventually, I’ll get around to creating similar lists for other markets.
• Mobile Techies & Bloggers:  This is perhaps the most interesting list – everybody out there that I’ve encountered so far on twitter whom I think has something interesting to say about mobile.  I tried to be discerning here as there are a lot of people who are tweeting about mobile.  I didn’t not limit myself to folks in the USA, but I did try to limit it to those who tweet primarily in the English language. I’ll keep tweaking this as we go.  I’m sure I’ve overlooked a few obvious folks here… sorry in advance. 

This is still very much work in progress, but if you’re a mobile junkie, eavesdropping on these lists should help you very quickly tune into the tweets that matter.   I’ll be adding some addition mobile-related categories in the future.  If you find this useful, a  retweet would be greatly appreciated!

Google Latitude is available on your iPhone via Safari (e.g. a web app) and not as a native app. The browser requests the user for permission to access the phone's location API.

This morning I came across this interesting and well-written article on the current state of affairs with regard to mobile app stores.   I think the author’s forward looking comments are reasonable if you limit your outlook to a year or two,  but there are a couple of things to consider with regard to app stores in the long term.  First,  the common presupposition made is that app stores will remain a relevant if not primary way users obtain apps for their phone.   From a purely technical perspective  I would suggest we should not ignore the possibility that rich Internet apps eventually begin to displace the need for native app installs, and eventually the need for mobile app stores.  As HTML5 continues to evolve and the underlying mobile platform becomes more accessible to web app developers, what advantage is there in downloading an app, especially when the data seems to suggest that mobile app retention rates are surprising low (25% on average!)?  It seems to me that web-based apps make perfect sense for a very large number of mobile apps that today are typically one-shots from the end user perspective.  Here at MASL our students have already built some very clever iPhone apps entirely in Safari.  Once a shortcut is added to the home screen it is indeed very difficult for the average user to discern whether or not its a native app or a web app. (We intend to do the equivalent of a “Pepsi Challenge” to actually measure this – look for more details in the future.)    Google Latitude on the iPhone is an early example of using the browser as an alternative to iTunes App Store.

That brings us to our second  point.   From a commercial perspective, Google is shaping up to becoming a pivotal stakeholder in the future mobile application ecosystem.   As I pointed out a while back, its raining Androids this Fall.  (For a much more up-to-date and complete listing of confirmed and rumored Android devices see the list that TechCrunch recently compiled.)  Every Android device I’ve used to-date requires you to become a Google citizen (you need to authenticate with a Google account or create one if you don’t have one) before you can use the device, and from that point on your mobile device is very tightly integrated with the Google cloud, and all the data and services you know and love (email, calendar, maps, search, etc.) are accessible from your mobile without the user installing anything.  It makes perfect sense for Google to gradually nudge the mobile application ecosystem towards a model in which the browser is the primary vehicle for third party application providers to access and integrate with Google services and data in the cloud. This also makes a lot of sense for the end user given the current app usage patterns and in the end seems to raise some interesting questions about the long-term viability of the mobile app store model.

I saw a couple of interesting videos this week that are worth taking a look at. The first one is about testing mobile application. So if you have an app that targets a multiplicity of handsets, all with different form factors, technical specs, and service providers, how can you go about testing your apps? Its simply not feasible to acquire all the phones you need to test on, and even if you could you’d still have to worry about setting up service plans, etc. Worse yet, perhaps you’re targeting a non-local market and want to test your app abroad on a particular carrier, etc.

The MOTODEV guys recently interviewed David Marsyla of DeviceAnywhere.com. David’s company offers the “ultimate mobile application testing platform”. Basically they have a network of over 2000 shared devices world-wide that they make accessible to developers via remote access. So in theory you could test your app on any device, on networks anywhere in the world without leaving your desk.

The second video was posted by Engadget and involves stress testing the actual mobile phones themselves. The video is footage they took in Nokia’s product test lab in California.  You’ll see them inflicting all kinds of serious misuse on the devices using an interesting array of robotic technology and other test apparatuses in an attempt to simulate the sorts of misuse you all inflict on your phones over the course of time. Makes for an interesting video.

The full engadget posting is here.

Today its not uncommon to run into people who think of human-like robots when you start talking about Android, rather than Google’s cool new mobile phone platform. This is likely to change dramatically between now and Christmas, at least here in the USA. In the past month a number of manufacturers and carriers have announced new Android-powered phones, and there are more to come in the days ahead.

Available today at a store near you …

At present, if you reside in the USA (we’ll have to write the international version of this post later…) your Android options are far and few between. Today you in fact have only three choices:

• HTC Dream (G1): Actually the first Android phone that became available (October 2008). It has a slide out QWERTY keypad and capacitive touchscreen. Its available on T-Mobile.
• HTC myTouch3G (Magic): This device became available via T-Mobile this past summer. No QWERTY keypad on this phone.
• HTC Hero (G2): This phone looks a bit like the G1, only minus the G1’s controversial “chin”. As of this past weekend, it has become available via Sprint Nextel. (October 11).

The other options you have here in the USA is to visit ebay or opt for the unlocked developer phone made available by Google (a G1 I believe…)

Coming soon …

If you can wait a few weeks more, the number of options available to you here in the USA will increase substantially:

• Motorola CLIQ (aka as DEXT outside the US): The US launch with T-Mobile is supposedly October 19. Its actually the same processor as the original HTC G1, but comes tightly integrated with your favorite social destinations via a layer of software added on top of Android by Motorola (MOTO BLUR).
• Motorola Sholes/Tao: According to latest rumors, this device will launch with Verizon as soon as October 30, but others indicate an early December launch.
• HTC Hero/Desire?? In addition to the Motorola android phone, Verizon is to launch a second Android handset from HTC this fall.
• Samsung Moment (InstinctQ): Originally announced by Samsung last Spring, Sprint Nextel has announced a launch date of November 1.

Coming not so soon …

There are also some more options that are further out that you’ll want to pay attention to if none of the above suit your fancy:

• Dellroid: a Dell manufactured Android smartphone to be available via ATT?
• LG GW620: officially announced by LG, this phone will become available sometime in 2010.

In addition to these two, you can be sure that the usual culprits (HTC, Motorola, Samsung) will be shipping a whole raft of new Android phones in 2010. In fact, last week Gartner forecasted that by 2012 Android will be the #2 smartphone, bested only by Symbian.  We’ll need a lot more devices out there than there are today in order for that to happen!

Do let me know if I’ve missed any notables in the first two categories above.

This semester I’m teaching an undergraduate CS course that has a weekly two hour lab session. Instead of going the traditional route of making up 4-5 programming assignments and assigning them over the course of the semester, I wanted to try and create a set of weekly labs that encourage the students to tinker and explore the concepts more deeply in an experimental sort of way. That is, I wanted to create a CS lab experience that was sort of like what one experiences in a biology course – start with a hypothesis, do some experimentation/observations and come to valid conclusions.

I initially thought about creating a document for each lab session that spelled out in cookbook style the various “coding” experiments, but the tedium tremors set in just thinking about what a massive effort that would be. What I really wanted is something that met the following criteria:

• Minimize “production” time: that is, once the basic ideation for a given lab session was complete (e.g. lab objectives identified, and the code “specimens” written/tested) I wanted to be able to produce the final lab “media” in 2 hours or less.
• Optimize the student experience: I wanted to use something that my students would find interesting and effective, and something they could refer back to after the lab session to review their work.  A thick written “lab manual” with lots of gory details would be dead on arrival.
• Easy to distribute:  just provide a single link and the students find everything from there, no matter where they are, or what kind of computer they like to use (its a real mixed bag – some kids like Linux, others OS X, and  some have Windows).

In the end, I installed ScreenFlow on my MacBook Pro and use it to create screencasts.   I provide the students with a lab assignment in the form of a PDF document that describes the lab exercise. However, instead of step by step directions written out long hand, I simply refer to a YouTube link of the appropriate screencast. The students are then asked to respond to questions about the screencast and are given the opportunity to modify/rerun the code and observe the results.

So far this seems to be working out quite well.  The students bring their earbuds to the lab sessions and most of the responses so far have been positive.  This is a format that they are already very accustomed to, and the 10 minute length limit in YouTube is a convenient goad in helping me keep each segment focused and to the point. We’re starting to see hits on the videos from various parts of the world along with some comments/ratings, so hopefully others can benefit from this as well!

Production time varies, but I’m definitely in the ballpark. Screenflow works very well for creating the screencasts, and the learning curve was fairly flat. Here’s a sample screencast introducing students to network programming in Java:

I’m linking to my complete set screencasts on my Screencast Tutorial page. In addition to the videos links, I’ve also included download links for the source code used in the screencasts.

I’m interested in comparing notes with others who have used this approach in teaching (CS or areas as well). In particular, let me know what tooling you have found useful for creating/editing screencasts and any other lessons learned.

MASL is located in C2-217 (second floor of Mackinac Hall in the CIS office suite)

The Mobile Applications and Services Lab recently held its first research group meeting at GVSU’s School of Computing and Information Systems.  In addition to myself, the group currently consists of five CIS graduate students and two undergraduate researchers. A variety of topics were discussed at the initial meeting, and perhaps most importantly we discussed our mission statement.  We expect this will be subject to some refinement in the months ahead, but this is how it reads at the moment:

“The Mobile Applications and Services Laboratory aims to combine emerging mobile technologies, social media, and pervasive network services in ways that effectively enhance the lives of real people and the communities within which they work, play, and socialize.”

The MASL Research Group meets weekly on Wednesday afternoons to discuss ongoing research projects.

We also discussed a vision statement with regard to who/what we want to become as we successfully execute our mission.

“By contributing original research results, enhanced educational experiences, and entrepreneurial opportunities, MASL aims to become established as a recognized center of excellence in mobile technology, within the GVSU community, the State of Michigan, and beyond.”

Our dedicated laboratory facility is located in C2-217 Mackinac Hall, and consists of new iMac and Dell workstations and a stash of new mobile devices.   There’s been a flurry of activity here in the past couple of weeks as students have begun working on various projects.  A lot of effort has also been put into getting our development environment in place (Thanks John!!)

The "black box" on wheels is the MASL "toy box" - our stash of mobile devices.

In the months ahead we hope to post details of our progress here on this page.  In the meantime, we’re interested in hearing from you, whether you are part of the GVSU community or beyond.   Do drop us a line.

MASL researcher John Spencer leads a discussion on iPhone development at a weekly group meeting.

TweetDeck for the iPhone.

Rick Broida over at CNET recently posted his top 5 desert island iPhone apps.  What follows is my choice of five apps were I stranded on a desert island.

1. Facebook: What better way to keep up with your friends around the rest of the world?    This is a fairly functional facebook client.  My only gripe is that there is not more ability to filter my news feed. Regardless of how much time I have to spare or how boring the island is I will NOT play Mafia Wars.

2. TweetDeck: From what I’ve tried, this is the best free twitter client out there.   It also integrates with Facebook.

3. FlyCast: Being a classical music nut, I got hooked on WMFT Chicago during the time I lived there.  WFMT is now streamed by FlyCast. In a day when good local classical music stations are hard to come by, I can now listen to the world’s BEST classical music station even from a desert island!

4. YouVersion.com Bible: As a person of faith, I derive much instruction and comfort from reading the scriptures.  This version gives me online access to many English translations, and downloadable offline copies of versions no longer subject to copyright constraints such as the KJV.  I can even practice my Dutch by reading the Statenvertaling.

5. Stanza: A free ebook reader program, with enough free classics available to last you a lifetime (Project Gutenberg) as well as the ability to buy more recent books as well.

Those are my five choices.  What are yours?

Recently I was speaking with a person who is managing a fairly sizable team of developers that is creating a mobile application.  They anticipate seeing the application launched within the USA in around six months or so. The person explained to me that their biggest challenge to-date is coding for and testing various Java ME versions of their client app which must run on hundreds of different handsets, all with different form factors, and on a variety of different operator networks.  When I asked why they were spending so much energy on their Java ME client the response was that their customer required the client to run on 80% of the handsets in use by consumers today.

If I were in their position, I’d spend more time and energy convincing my customer of the reality that is upon us and leave the Java ME slogging to my competitors.   The mobile application landscape has and will continue to change rapidly in the months ahead, thanks to strong growth and innovation in the smartphone category.   A recently published Gartner study reports that in 2Q09 the overall handset market declined 6.1% while the smartphone category increased by 27%.  If you are currently developing a mobile application or soon will be, here are 7 future proof assumptions that I think you can safely make.

1. You will stop porting and start creating. Moving forward, there will be a small number of highly portable mobile application platforms that really matter, and likely a few more that will be mostly irrelevant except for limited niche audiences.  Its somewhat early to forecast who all will be in which category, but it is likely that the iPhone and Android will be in the former.  From the application developer’s perspective, the good news is that gone are the days in which deploying your app meant building hundreds of different binary Java ME jars and testing them on myriad devices.  There will always be some porting or supporting of multiple app clients (e.g. an iPhone version and an Android version) but in general,  a small number of builds will cover large swaths of your intended audience. Not only does this mean you have a crack at launching a successful mobile application, it also means you will be able to spend a lot more time and $$ in the future on innovating and creating compelling mobile application experiences. The mobile application revolution is just beginning.

2. Your users will have unlimited data plans. Even if you did have a magical “porting machine” that could generate binaries for the vast majority of the legacy mobile devices still in use, you would still face a huge hurdle in that most users of such devices do not have data plans in which they can affordably download and use an application that requires network data services.  In the smartphone category, at least here in the USA the situation is quite different.  Many smartphones are purchased under contracts that require a mandatory data plan.   In addition, many of these phones also support WiFi which the user can take advantage of in addition to the wide area mobile network.

3. The mobile application gatekeepers will be around for a while, but they’re fairly broadminded. Even though it is gated, the Apple iPhone application ecosystem is a “sneak preview” if you will of how easy it will be to distribute mobile apps moving forward.  While Apple’s rejection of apps due to “objectionable content” tends to get a lot of media attention, the amazing number of apps in the store at present and the billion downloads seems evidence enough that its not all that difficult to make your mobile application available on the iPhone.    The gates for getting and keeping an Android application in the  Android Market are even lower. Nevermind for now the fact that the iPhone App Store currently sells 250 apps for every app sold in the Android Market!   Eventually these  gates will disappear altogether, but we’ll save that for point 5 below.

4. The user interface bottleneck on the mobile has all but disappeared. The mobile application UI was painful until the arrival of the iPhone.  Now things have changed dramatically.  The iPhone has proved that a mobile app can actually be a pleasure to interact with. Mobile app creators can safely assume that their target devices will have nice high res color display, an easy to use touchscreen interface with either a QWERTY keypad or soft keypad that makes text entry relatively painless, at least when compared to the multi-tap entry of the past.  Additional hardware features such as accelerometers and locative technologies can also be used to improve the user interface in innovative ways.   It seems that successful mobile speech interfaces will remain effective for the time being, only in tightly integrated application experiences, such as Google Mobile for the iPhone.  The technology and standards required for introducing an integrated distributed speech recognition modality as a generalized application service are just beginning to emerge.

Demo of the speech modality in Google Mobile for iPhone.

5. Rich Internet applications will eventually triumph over native installed mobile apps.  There are a couple of  factors to consider here.  First, the WebKit foundation all up and coming mobile web browsers (iPhone, Android, Palm Pre, etc.)  have in common should not hurt when it comes to writing web apps that run well on the devices that matter.  Second, a raft of new RIA inspired features coming in HTML5 should go far in helping you write web apps that look and feel like native installed apps.  To get a glimpse of what’s coming down the pipe in HTML5 be sure to watch some of the 2009 Google IO presentations.  To be clear, native apps are still important today, and you may very well have to create iPhone/Android apps to kick start your mobile app franchise in the near future.  However, we believe these emerging developments will eventually create a situation in which the complications of authoring and deploying native applications are supplanted by rich Internet apps that really do run everywhere with minimal effort.   Companies such as Appcelerator are already pushing the envelope in this area, and we expect to see a lot activity moving in this direction.

Google IO talk on HTML5.

Appcelerator talks about their Titanium platform.

6. De facto exploitation of features that for the most part uniquely belong to mobile. By default your users will expect their apps to fully exploit the unique capabilities of the mobile phone. The mobile phone was a communication tool long before it morphed into a general purpose application platform.   Moving forward people will expect mobile applications to incorporate communication and social media features.   They will expect to be able to leverage their social graph in a meaningful way in any mobile context they happen to find themselves.  In addition, users will expect the context sensing equipment (camera, location, audio, etc.) that is now standard on virtually all smartphones to be utilized by their applications.   Locative app features will abound and be standard fare in mobile apps moving forward.

7. Battery life will continue to be a problem for your users. All of this good stuff does not come for free.  Those bright screens, multiple radios, etc. will very quickly take their toll on today’s portable energy solutions.  Instead of charging their phones up every 36 hours, users will find themselves charging up every 8 hours!  Developers need to be conscious of this and develop their applications accordingly.