It’s not uncommon if the first thing you do in the morning is grope around the bedside table for your phone. Who can get out of bed without checking the stocks, checking email, checking Facebook. Or even before going to bed at night, the last thing many of us do is check Instagram, fire off a final tweet, or confirm what time boxing class is the next day. What is it about these apps that have inherently integrated them into our daily lives? There was a time before mobile applications when people didn’t NEED to check mobile apps, but that time occurred simply because they didn’t exist. Now that they do, it can be nearly impossible to imagine what life was like pre-app. How did the most addicting apps become so...addicting? Yet even more importantly, how can your app become one that users can’t get through the day without? Plug Into the Routine The apps that are used the most have everything to do with what their user does in day-to-day life. Think about the ones you use...apps that track exercise and eating, apps that help manage schedules, apps that provide music to help you hum through the day. These are the winners in most people’s lives because they are with the users as they go about their day, and even make it easier for them to do the activities they like. If you can fulfill a need that fits into a user’s daily routine, it’ll be addictive. Integrate with Other Services Some standalone apps have good reason to be just the way they are. However the golden handcuffs are fastened when your app can integrate with apps and services your users already love. For example, PayPal is a well known money transfer service, allowing businesses to accept funds and allows friends to send money to each other. All that is needed is an account holder’s email or phone number and poof, money is sent. However the hassle arrives when the payer must look up the phone number or email address of the person they wish to pay. This can be just as much of a hassle as getting up to get and enter the credit card, which can inhibit the transaction from occurring altogether. Then came along Venmo, a money sending mobile application integrated directly with Facebook. Upon sign up, a user immediately connects to Facebook and accesses the Facebook user’s profile and friends. Once bank account information is initially entered, the user can easily send funds to anyone on their friends list who has also activated the Venmo app. This integration makes it much easier to send money to friends, and removes the barrier of looking up any sort of account information. Because of this Venmo quickly became a go-to app for savvy spenders, and eventually were acquired by PayPal.  Talk to Your User Send timely notifications to let your user know you’re there. You’re competing with a heavy amount of noise both from the users app filled phone and with the busy world around. In order to become an app worthy of daily use, your user should be regularly aware of its existence. For example, if they haven’t logged in for a day or two, send a gentle reminder via push notification to remind them to check in. Perhaps you can gain the user’s email address. If so, send updates on what’s going on with your app to keep the user informed - and your app top of mind. Get Personal Have your user enter personal information, if it makes sense in the context of your app. From there, personalize their experience. When they log in, greet them with a, “Hello Brent!” or even ask them how their day is going. If you know their time zone you could go even further and say, “Good evening, Brent!” The sweetest sound to any person’s ear is their own name - so use that Psych 101 tidbit to your advantage to get your user hooked on your application.  Make it Fun Regardless of if your app is for business or play, most of the time you can still have fun with your user. Gamification is as addicting as sugar, so get your audience engaged in ways that make your app feel more like a game.* Perhaps you can add a host character who guides the user about the app, making it fun and friendly. Or encourage more activity by unlocking new features with continued use. Awarding points or prizes in some way is a great way to make your user feel rewarded - and keep them coming back for more. *If your app is a game, well, make sure it’s a really fun game.  Keep an Eye on User Activity Monitor where your users spend their time. What portions of your app are they using? Which are hardly opened? If you can determine usage you can gain valuable insight into what is working for your app, and build upon the features that intrigue and engage your audience. There are some great tools available that can help you with this, such as Google Mobile Analytics or Flurry Analytics. Just remember that what is taking up valuable data space could possibly better be used otherwise, which can make your app the attractive solution to getting the user through their day. Connect with Friends Similar to our point about integrating with other services, if you can connect your app to the user’s community, all the more reason for them to stay engaged with your app. While we know that we talked about dating applications recently, we can’t help but hammer on the issue of how genius it is to connect daters with people who aren’t entirely strangers. In our particular article we talked about Pear Friends, yet there are other dating applications that utilize user’s friends to get better results when providing matches. One such app is called Hinge, the app that helps users meet new people through friends by connecting daters only with people within the parameters of that user’s social circle. It does this by plugging in directly, again, with Facebook. From there the app searches through friends of friends to determine what kind of people may be a good fit. Using this strategy makes it much more addicting for daters, as infused with it is the excitement of learning who friends are friends with, and the added security that matches are not complete strangers. The success of your app depends on having users. Giving your users a reason to use your app daily gives them reason to talk about it with their friends, thus widening your user base and making you more successful. If you’re ready to get started making that app dream a reality, let us know how we can help you get started.  

This is a question that we go through with nearly every mobile client we work with at Barefoot Solutions. Mobile technology is progressing at breakneck speed right now and it's very difficult to keep up. So to start, what are the technology options for launching a mobile strategy? While there are an infinite number of variations, the options can mostly be put into 4 buckets: Mobile Websites Mobile Web Apps Hybrid Apps Native Apps Mobile Websites are simply websites that have been optimized for mobile devices. A good example of this can be found at http://m.techcrunch.com. Changes to the layout are made by recognizing the user agent as a mobile device and optimizing for its limitations. This can include removing ads, increasing the size of clickable areas, and most importantly, accounting for the smaller screen size. Mobile Web Apps are still mobile websites, and thus must be accessed via a phone or tablets web browser. The difference between a mobile website and a mobile web app is that mobile web apps are built to mimic functionality of native apps. By adding controls like date pickers, tab bar navigation, and other native feeling controls, this gives the user the experience of using a native app. Typically these are built using frameworks such as Sencha Touch or JQuery Mobile. These frameworks are effective because they have already built most of the common controls using HTML5 and Javascript. Building all of those controls from scratch would be a significant undertaking, but JQuery Mobile you can focus on functionality, rather than building the sometimes complex user interaction necessary for mobile devices. Hybrid apps also utilize frameworks, often built with HTML5, Javascript and CSS, to produce native-feeling apps. Some examples are Phonegap and Titanium Appcelerator. The difference between a hybrid app and a mobile web app is that the hybrid apps are actually compiled and treated as native apps. This means that, on your iPhone for example, a hybrid app must be downloaded from the app store, and will live as an app icon on your home screen. Hybrid apps are appealing because they allow you to develop only a single app, but then compile for the various app stores and be available on multiple platforms. Another benefit of hybrid apps is that they have access to the phone's hardware. Access to the accelerometer, image gallery, camera, bluetooth, and other sensors on the phone are often a requirement for the more advanced apps. Finally, we have purely native mobile apps. This means that they are written in Objective-C for iPhones, or Java for Android applications. They are compiled, and submitted to the app store for distribution for that devices particular users. Mostly, native apps have to be built as a separate piece of software for each platform, and are able to share very little code. So if the desire is to make your app available on iPhone, Android, WinPhone, and Blackberry, you would need to build four separate apps. So with those as the options, what factors should go into deciding on a platform? To start, it's important to identify the goals and limitations of your mobile strategy. Then you apply those goals to the four factors below to make a decision. Cost Mobile apps become more expensive as you get closer to the fully native experience. A mobile website can often be implemented by altering layout and stylesheets of an existing website, and as such is a low cost product that can be accessed on any phone or tablet with a web browser. Native apps, on the other and, require quite a bit more development time, which then gets multiplied by the number of platforms that need to be accessible. As such, native apps are the most expensive option, by far. User Experience If this decision was based entirely on cost, then a mobile website would be the obvious choice. But what about the user experience? Unfortunately, native apps, while the most expensive option, also provide the best user experience. By interfacing directly with the native SDKs, native apps have a very fast and responsive UX. Think of the difference between using a desktop app like Microsoft Word, versus Software as a Service like Google Docs. Because Microsoft Word is a compiled and installed application, it directly interfaces with your machine and allows it to be more powerful, and responsive. The same holds true for native apps. Further, native apps have controls like pickers, navigation tabs, action bars, and others that are immediately recognizable to users of a platform. When building a single app for multiple platforms, you must find commonality amongst those platforms and therefore can't entirely mimic a native experience. While this will work for some apps, others, particularly those that are entirely consumer facing, need the native UX to provide users what they have come to expect from their apps. Difficult to develop and maintain Many organizations now have in-house web developers, or at least people with some experience with HTML/CSS. This makes it possible for some organizations to build a mobile website or mobile web app without having to hire outside of the company. Native apps however require a very particular skillset. Objective-C developers, for instance, can be difficult to find and expensive to hire. While it may be feasible to hire a firm for the initial development of your app(s), there is also the matter of continually managing this relationship to account for updates, bug fixes, operating system upgrades, and other required maintenance over the lifetime of the app. Depending on resources this may not be feasible for some smaller organizations. Reach Mobile websites and mobile web apps are available on any device that has a web browser. This is basically any feature phone or smartphone these days. As such, they have the furthest reach with the lowest cost. Hybrid apps can also be available on multiple platforms for only the cost of building a single app. Further, along with native apps, they have the added benefit of placement in the various app stores. This allows apps to be discovered by users in a way that just isn't possible with the mobile web. This also allows the possibility of reaching high in search rankings, or earning a featured placement in an app store which can provide a serious spike in downloads. So what approach should you choose? It seems to be like the odds are greatly in favor of the non-native options, but very often that is not the case. As I mentioned, the user experience on non-native apps is just not where it needs to be. Even with hybrid apps, buttons can take a half-second longer to respond to a tap, and scrolling can get slow and choppy. In the beginning of 2011, Facebook's mobile app took a largely hybrid approach. They were faced with considerable user unrest, and suffered a fairly low rating in the app stores. In the middle of the year they re-architected to a much more native experience. Their apps are now faster, more responsive, and the user feedback has improved considerably. At Barefoot Solutions, we always recommend native for any purely consumer facing app. Period. If you want to have a chance at gaining significant traction, it is imperative that you provide the best User Experience possible. It is often better to launch on only a single platform, with an excellent user experience, versus launching a mediocre experience on all platforms. When we start talking about internal apps, mobile web apps and hybrid apps become a much more cost effective solution. For example, if you're building an app to help your sales staff in the field, and this staff uses a variety of devices, it often makes sense to build a hybrid app. This will allow most of your staff to use the app on their devices, and they will most likely be willing to look past the slight lack of performance. If you are a restaurant that just needs contact information, directions, and a menu available on customer's phones, then a mobile website is probably the right strategy for you. Overall, this is a decision not to take lightly. Jumping from one strategy to another often requires an entire rebuild, so it's important to get this right the first time. At Barefoot Solutions, we're happy to provide a free consultation to discuss your mobile strategy and provide an in-depth look at what might be best for your startup or existing company.

It’s true - there is a clear trend we are abandoning our desktops and hopping on phones and tablets to access the Internet. 2014 figures range from 23 - 55% of users Interneting via mobile, with the heaviest mobile useage, 55%, occurring in the United States. So we don’t need to spend any time convincing you: You need a web option for your business. A percentage of users will access via mobile device. Phew, that’s out of the way. The conversation, rather, is around how you want your users to interact with your site - mobile web or native app. Mobile web is typically the cheaper upfront option, which allows space for small businesses to find reason to avoid the expense of building a native app. Yet the app is increasingly taking over the mobile market, largely due to superior UX, are generally more powerful and are very much a hip trend. 2014 research in a much cited Flurry study shows that apps, “commanded 86% of the average US mobile consumer’s time, or 2 hrs and 19 minutes per day.” Most of that time, 60%, is spent on gaming and social media sites, clearly demonstrating the entertainment component of the native app. That's right, we haven’t completely forgotten about wonderful wastes of time like playing Angry or Floppy Birds. Fun components aside, at what point does your growing business need a native app - or do you even need one? If we know that internet users are increasingly accessing via mobile, and most of that time is spent via native app, the last thing you want to do is get left behind without providing the option users are clearly demanding. Here are some considerations to help you make the decision to go app or opt not: Your Specific Business Needs As with anything, the decision is based first on careful consideration of your particular business and customers. What do you sell and what are your clients like? Social? Utilities? Marketplaces? Then let’s be crazy honest, an app is for you. But if you, say, work with clients primarily on a face-to-face basis as a small restaurant, coffee shop, or even as a lawyer, you can likely get away with a well thought out responsive design. Additionally if you rely on search engine traffic, that’s a good indicator you can perhaps stick with mobile web. Commerce Mobile commerce (mcommerce) is anticipated to continue trending upward as we march on through the 21st century. A recent study predicts that 25% of commerce will take place on mobile by 2017, which again is a helpful reminder that your users are on mobile. If you have a commerce option, there certainly are ways via mobile web to effectively facilitate transactions. But if you are selling, you want users to consistently keep buying - and the native app has been found to be linked to brand loyalty. Customer and Brand Loyalty Get real with yourself - do you have loyal customers and/or solid brand recognition? Native app is best for when you have a loyal customer base. For example, I have a smartphone like most breathing Americans, but it can take me a while to make the commitment to download a mobile app. Often when I visit sites I’ll be asked to “Download our App!” which I often bypass the first time I see this suggestion. You may behave differently in your Interweb mobile browsing, but to me, often times I just want the information I’m looking for and to be done with it. But as time goes on and I use a service more than once, I’ll make that 2 minute commitment to download an app. I eventually come to the realization the app will be much easier for me to access if I’m going to continue visiting. While I still deal with download commitment phobia, it is clear that engagement on the native app is increasing as, “the average time spent with mobile apps in the U.S. grew 35% in 2012 to 127 minutes per day, while average time on the web declined 2.4% to only 70 minutes per day.” Responsiveness How important is it to provide your users with a fast response? Yes, anyone would say, “Very important!” Yet in all honesty, not every site needs a speedy user experience - but you might. One of our favorite things about Native apps is how one tap will instantly move the user on to where they want to go. Much faster than irritatingly pausing for that please-wait-while-we’re-connecting-to-the-internet spinner to finally stop. The other consideration is if you do want the superior responsiveness of a Native app, you will likely be trading for a lower accessibility than you can achieve with mobile web. End Goals At the end of the day, what are you after? Whether it’s to sell more, increase engagement, or communicate in a more targeted way, arguments can be made for either native app or mobile web. The superior UX of a Native app will likely encourage greater activity as they encourage a deeper engagement with the user. But if you are trying to get as many people to your site as possible without a significant number of features available, you can likely get away with a mobile site. Remember, responsive is not just about fitting everything on the screen. Native app is not just about joining the trends. Your company has a specific set of needs and so do you. As we continue to track mobile usage, it seems clear that users will continue to download apps - and if you have an idea for an app, yours should be one of them. by Joni Erdmann