• Prompt Users To Upgrade Your App With In-App Messaging

    Share
    In-app messages can prompt users to upgrade to the latest version of your app

    Release the minimum viable product, iterate often, and respond to user feedback. These are all pretty standard beliefs for the development teams of the world. Unfortunately, the user isn’t always interested in upgrading. Maybe they haven’t noticed the small upgrade overlay on the app store icon or perhaps they don’t know the value of your latest version.

    Today I’ll walk you through two complementary in-app messaging campaigns that will help increase the likelihood your users will upgrade to the newest version of your application.

    As a refresher, the Localytics in-app messaging platform allows you to send rich, customized messages, specifically crafted for individual audience segments directly based on your analytics data. Because it is based on your user segments and in-app triggers, you are able to refine the experience to best suit the right audience rather than a broad-stroke, non-targeted, campaign.

    Campaign 1 – Standard Upgrade Notice

    Our first campaign will be similar to what you’ve seen throughout apps far and wide; it will target anyone who launches an older version of the application. From the marketing tab, create a new campaign named “Broad Advertisement”. After naming the campaign you have two options on what your campaign will look like, you can upload your layout and message or you can easily build a creative right in the Localytics interface. This creative should have some descriptive text calling out the benefits of the next version (e.g. “Fixed that annoying bug that causes app to crash” or “Now with more bacon!”) and a call-to-action, prompting users to click through to upgrade to the latest version. Through the Localytics Creative Builder, you can ensure that the typography and color fit within your specific style guidelines.

    The goal of this campaign is to target all users of the previous version of the app. For this campaign, we’ll filter our users where the dimension “application version” isn’t the current application version. We want to target all users who are even remotely active; any user who’s had at least one session in the past month will be our qualifying action. This combination of filtering and qualifying behavior ensures we’re only targeting users who are even slightly active on any older version of the app.

    With our creative done and recipients identified, we’ll identify an aggressive event trigger. When selecting an event trigger, pick an event that you’re sure will be fired early into a user’s session. Picking an event that is almost guaranteed to happen for every user ensures that most users will receive the campaign.

    Schedule this campaign to run for 90 days.

    Campaign 2 – Targeted Notification

    Our second campaign is more granularly targeted. We want to target only users who are engaging with features that have improvements in the newer version of the application. For purposes of our example, the V1 of our app has sharing functionality. V1 allows users to share to Facebook. In the V2 release, our app enhances sharing to include Twitter, SMS, and email in addition to Facebook.

    From the marketing tab, create a new campaign named “Targeted Upgrade – Sharers”. Develop your creative, using either the creative builder or uploading your own. Your descriptive text should be specific. In our sharing example something like “In V2 you can share even more ways, we’ve added Twitter, SMS and email sharing”; the call to action should, as in campaign 1, prompt users to click through to upgrade.

    The goal of this specific campaign is to target just users of V1 who are utilizing the sharing feature, which is enhanced in V2. As in campaign 1, we’ll fitler our users where the dimension “application version” isn’t the current application version and target users who are remotely active.

    Unlike campaign 1, we don’t want a trigger that will fire early in a users session. We want to hit the users at just the right place and just the right time. As we are targeting just users who are utilizing the sharing feature, we’ll want to trigger the creative appearance on the “sharing summary” event.

    Schedule this campaign to run for 90 days.

    Hopefully every release of your app adds valuable features for your users, and you can follow this pattern to drive upgrades by targeting frequent users of upgraded features.

    Wrap up

    After activating both of these campaigns, your users will start receiving the upgrade notifications. To help you further understand the impact these campaigns have, navigate to the app versions by day report in your Localytics dashboard. In that report, add a comment on the day you’ve activated these campaigns; going forward you’ll always have that indicator as a reminder. Running these campaigns for a few weeks should reduce the number of users you have on older versions of your application.

    In-app messaging - take action on your mobile analytics

    Free Webinar: Introduction to In-App Messaging
    Learn how to deliver analytics-targeted messages to your mobile users with in-app messaging.

    Watch the webinar


  • News Consumers Learn Of New Pope Via Mobile

    Share

    It’s been an interesting day here at Localytics. This afternoon, we learned that white smoke rose from the Vatican, announcing a new Pope had been chosen. The way we found out was by so many people finding out themselves via mobile apps.

    About 2:07 PM US Eastern Time, we noticed a massive spike in usage across apps running Localytics. The spike peaked about five minutes later at significantly higher than our usual rate, indicating a huge amount of users delving into the Papal news via mobile apps.

    Pope news found via mobile

    It’s important to note how international news like this is being disseminated – as apps become more ingrained in the way people consume news, media organizations have to have a strong app presence. Tools like in-app messaging can help deliver breaking news, and detailed analytics can provide organizations with information on what subjects particular users want to be notified about.

  • Downloads Don’t Matter – Whiteboard Wednesday

    Share

    Transcript

    Hi. My name is Daniel Ruby, and I’m the Director of Online Marketing here at app analytics and marketing provider Localytics. Welcome to this Whiteboard Wednesday.

    Today we’re going to talk about why downloads don’t really matter to your apps.

    If you go back to when brands first started to move into the app store, there was a straightforward but murky process about determining how successful your apps were. Your “funnel” went from the app store to the number of downloads, then to something of an undefined, “I have no idea” section, and then you had to assume that there was a profit at the end.

    Fortunately in the meantime companies like ours have evolved the idea of app analytics, so that this undefined middle part is no longer a bunch of question marks, but rather a measurable part of a true marketing funnel.

    Like with any marketing effort the first thing you have to do is define your goals. This is different for everyone, as different organizations will have different goals. For newspapers the goal may be getting a user to pay for a subscription. For an mcommerce app it’s getting somebody to buy something in the app.

    Once you’ve defined your end goal you can start looking at how users are actually interacting with and navigating through your app.

    The first step of the app marketing funnel is from download to launch. You’d be surprised at how many people will download an app and never launch it – sometimes if they don’t launch it immediately after downloading, they lose that top of mind thought process and never come back to it. Alternatively, maybe you’ve paid for some downloads and they weren’t targeted as well as you’d like – it gets onto a user’s device and the user thinks “you know, I’m not really the right person for this app,” and they never launch it.

    The next step in the app marketing funnel is to go from launched to engaged. That’s a very important step – we’ve done some research in the past showing that of all apps that are downloaded and actually launched, twenty six percent of them are launched only once. That’s one of four apps in which the target user downloads it, fires it up, says no thanks and never comes back.

    It’s very important then to use your analytics to determine how people get from launched to engaged. As with your end goal, your definition of engaged may vary – it could be based on the amount of time somebody spends in your app, it could be based on the number of times somebody launches your app, or could be based on the number of events somebody actually triggers while using your app.

    Once you’ve started to leverage your analytics you should be able to find a few common threads – a few paths that people take from launch to engage which can help you determine what your users are really interested in.

    Your next step is to take these users from engaged to converted. At this point you’ve got an engaged user actually interacting with your app regularly. They like your app. They like your content. So how do you give them that little push to actually convert on whatever your goal may be?

    Similarly to going from launched to engaged, you’ll find a few common threads, a few common actions, and a few common paths that people take going from an engaged user to user who has completed your goal. That should be your final step: figuring out what parts of your app you should focus on to maximize your app marketing funnel and achieve the goals that you’ve set out for your organization.

    And so how do you do this? It could be as simple as going to Localytics and downloading our free analytics tool and instrumenting it into your app.

    Either way it’s very important to note that downloads are no longer the end all be all statistic for your app and there are analytics now to give you a full three hundred sixty degree marketing funnel for your app users.

    Again my name is Dan Ruby, thank you very much for joining us for this Whiteboard Wednesday and I hope to see you next week.

  • Cohort Analysis Overview – Whiteboard Wednesday

    Share
  • In-App Messaging Campaign – M-Commerce Deep Dive

    Share

    M-commerce is one of the fast growing and unique segments of any retailer’s engagement with their buyer. With the rapid adoption of mobile, especially in commerce, it is vital that your marketing campaigns be more engaging and relevant to mobile users than ever before.

    Today I’ll walk you through setting up a campaign that will increase sales.

    As a refresher, the Localytics in-app marketing platform allows you to send rich, customized messages, specifically crafted for individual audience segments directly based on your analytics data. Because it is based on your user segments and in-app triggers, you are able to refine the experience to best suit the right audience rather than a broad-stroke, non-targeted, campaign.

    Adding items to a shopping cart and never checking out, what could be worse? This behavior is frustrating as a marketer and something that is yours to improve. You continually want to find ways to improve those major conversion events throughout the business, and with mobile it is even more imperative to optimize the experience given the small form-factor with which the shopper is working. In the M-commerce world, the major conversion event is purchasing. With Localytics mobile app analytics you can create a countless segments, e.g. one that tracks users who have multiple items in their shopping cart with a total value greater than $100 but never check out. Then you can create a campaign that targets this user segment. The campaign should encourage them to checkout and perhaps offer promotions to help facilitate the checkout conversion.

    How can you start a campaign like this in your app?

    Step 1 – Tag the app & build the segment

    Localytics - segment builder

    First, as you’re working through your Localytics implementation, create an event for “item added” to shopping cart, your application likely has a way to track this already. This event will track how often items are added to the user’s shopping cart. With this event you will likely want to add a couple relevant bits of information about that “item added” e.g. item name, value, quantity. Then, using the same approach used to create the “item added” event, you’ll create an event for “check out successful”. This event will track each time a user successfully completed the order process.

    From the Localytics dashboard, navigate to the Segment screen and create a segment of users who, in the past 30 days, did the “item added” event and then never did the “check out successful” event. Name the segment “Non-purchasers with items in cart” and save it. This segment will now track all customers in the past 30 days that have added an item to the shopping cart and never checked out.

    Step 2 – Build the campaign

    Now that we’ve built a segment of users who have items in their shopping carts and haven’t checked out, we can target those individuals directly.

    From the marketing tab, create a new campaign named “Free Shipping – Stale items in cart”. After naming the campaign you have two options on what your campaign will look like, you can upload your layout and message or you can easily build a creative right in the Localytics interface. This creative should have a some descriptive text and a call-to-action, prompting users to click through to their shopping cart or a pre-checkout page. Through the Localytics Creative Builder, you can ensure that the typography and color fit within your specific style guidelines.

    The goal of this campaign is to increase sales from a known group of interested buyers; as such, we can be aggressive in when the creative is displayed. We will want to make sure when we are selecting our targeted recipients that we use the segment “Non-purchasers with items in cart” which we created in Step 1 above. In addition to using the segment, we want to make sure that we target shoppers that are continuing to browse through products therefore we can define a qualifying action or event such as “category viewed”. To make sure that we don’t overwhelm the shopper with messaging we will qualify them for this messaging if they viewed a category four times in the last five days.

    Once we know who we are going to target, we need to decide when to deliver the message via a trigger. You could use an event trigger such as “product viewed”. Using this event as a trigger allows you to not only entice the user to add an item to the cart as they are already interested in a product but will also help facilitate the completion of the purchase within that session.

    The conversion event for this campaign will be the “check out successful” event. Setting this event as the conversion event will let us see how many people saw the creative, how many clicked the call-to-action, and how many eventually checked out. Schedule this campaign to run for 365 days.

    Step 3 – Review performance and adjust accordingly

    Localytics marketing campaign performance

    With your campaign active, you will begin to see results within the campaign dashboard. You will see the number of impressions, clicks and successful conversions. In monitoring this dashboard, you may see your campaign get many impressions but few clicks. If the trend continues, should consider testing your campaign further using an A/B test. As part of Creative Builder, you can create or upload multiple creatives for each campaign and track effectiveness of each. If your campaign is generating lots of impressions and clicks, but few conversions, it may be a sign that your promotion is not enticing enough to push the shopper to purchase and you could reconsider other promotional options.

    Wrap up

    After running this campaign for a few weeks, you should see fewer people with un-purchased items in their shopping carts. You should continue to monitor your analytics for other areas where you could run a campaign. Other areas that may be worth targeting: unspent reward points / gift card balance, users purchasing as guests rather than registered, and limited time / flash sales.

  • Structuring Your Organization For Mobile – Whiteboard Wednesday

    Share

    Transcript

    Hello everyone, my name’s Richard Sgro and welcome to Localytics’ Whiteboard Wednesday. Today I’m going to talk to you about structuring your organization for mobile success.

    Today we’re gonna talk about three different organizational structures to help you get to the mobile goals that you have.

    The first model is the one-team model. In this organizational structure the team that’s building your core experiences, having developed your core brand experience, also understands mobile technology, your brand’s challenges and your users. In this model that core team directly transitions from creation of your desktop or mobile experience to the mobile experience, implementing it themselves.

    There are some challenges to this model – your core experience team can often think about your brand experience in one set way and may think of mobile as a complimentary or supplementary experience. They may struggle to think about the mobile first scenario. In addition, your team’s coding skillset, be it on the desktop or on the web, often doesn’t directly transition to the mobile world.

    The second model that we’re going to discuss is the insourced model. In this model your core scenario team continues to focus on your core web and desktop branding experience. They build and focus on this overarching experience and conceptualize all the different scenarios and angles on the desktop or on the web.

    As part of that process they define some mobile scenarios. As they define those mobile scenarios they work with an internal team of mobile experts to get them developed. Thus you have a second development group, specifically mobile experts, and they spend their time solely thinking about your mobile presence.

    The challenges of insourcing are different than those of the one-team model – for one, collaborating internally in organizations oftentimes results in challenges in prioritization. Your internal mobile-first product team may have a number of different internal partners, and your scenarios or your application may not be high on their list.

    The third and most common model we see is the outsourced model. Your team has an established, excellent set of core experiences – they understand the user and they want to continue to focus on the overall brand experience. Working with your scenario team, a product manager or product owner comes up with your organization’s mobile requirements and hands them off to an external third-party. After some time that external third-party hands back a completed mobile experience.

    This is really great if you’re looking to get a mobile experience out the door quickly, but there is a monetary cost associated with outsourcing your mobile development, and oftentimes it’s higher than the other two models. It’s also important to think about the long-term implications of having a external third-party build an application. Who owns the bugs if there’s an issue found? Who’s going to troubleshoot it? Who owns first line support?

    So we chatted a little bit about each of these models and when making a decision, it’s important to consider the specific needs of your organization. If time is vitally important – you’ve got a great experience launching on the web or on the desktop, and you really need to make sure that you’ve got a mobile presence – outsourcing may work really well for you.

    If in your organization has a strong group of mobile-specific experts, the insourcing model may be perfect for your organization – just be cautious of the challenges of group collaboration.

    If you’re fortunate enough to have an organization with a very fungible development team, I would generally encourage you to think about the one-team model. This allows your organization to think through all the scenarios from all the different angles, allowing a unified team to build great experiences on all the screens that your experience is on.

    So these are the three different organizational models, I hope you enjoyed our chat today. As I said before my name is Richard Sgro and this was Localytics Whiteboard Wednesday.

    Thank you very much

  • Three Campaigns Every App Should Consider

    Share

    With the broad release of the Localytics contextual marketing platform, I wanted to share with you three campaigns that every customer should run. As a refresher, the Localytics contextual marketing platform allows you to send rich, customized messages, specifically crafted for individual audience segments, automatically, based on your analytics data. Because it is based on user segments and in-app triggers, if you can analyze something, you can message to it in-app.

    One of the most common questions I get when chatting with customers is “What campaigns should I run”? While the answer to that question varies by app type, industry segment, and goals, there are three campaigns that I think every app should run.

    Rate my app

    Rate my app in-app message example

    You’ve got your app in the app store and no one is rating it. A high rating can significantly increase your app’s adoption while also, potentially, bringing you fame and fortune. There are thousands of different ways to prompt users to rate your app, and a quick google search yields hundreds of code snippets.

    Using Localytics in-app messaging, you can target all users of your app and request they rate it. But let’s take this concept to the next level. It’s not always desirable to have all your users rate your app. All things being equal, you’d want the users who were most deeply engaged with your app to rate it. They’d be best qualified to write a compelling review. Based on the analytic information generated by Localytics, you can target just those users. As an example, you could target users who had both many sessions per week and who triggered a number of events in the core functionality of the app.

    Upgrade to the latest version

    Upgrade your app version in-app message example

    You’ve added great features and you fixed all the annoying bugs. Your new users get a great new experience, while your existing users plod along enjoying v.Old. As with app rating, there are a number of different ways to get users to upgrade. Denial of features, pushing notification, or simply letting them continue all work, to some degree.

    With Localytics contextual marketing, you can prompt a user to upgrade at just the right time. Using the analytics you’ve already implemented, you can target a campaign for users as they are active in a section that, if upgraded, would have new functionality. Additionally, the message your user sees will have a link that will take them directly to the itunes store to upgrade, reducing potential drop off. Also, because you know the section your user is active in, you can gear the message specifically to that area. As an example, if I was in the sharing section of an older version of your app, you could prompt me upgrade by tell me about all the great new sharing features in the new version. Prompting me at the right place and right time is much more compelling than a simple message to “upgrade now”.

    Outage notification

    App outage notification in-app message example

    Your app is running smoothly. Your adoption is growing in leaps and bounds. Then, the cloud service upon which you depend, suffers a major outage. No one can access your app. You hit all the social media channels; but people opening your app have no idea why it’s not working. You could push an app update that lets users know what’s going on, but that requires both app store approval and user action.

    With Localytics contextual marketing, you can broadcast a message out to all users. Sending an in-app message does not require an app update and allows you get your notification users within minutes of an outage. Additionally, once the outage is over, you can quickly remove the outage.

    I hope these campaigns give you some idea of how to get started with in-app messaging.

  • Key Metrics for Mobile and Web Analytics – Whiteboard Wednesday

    Share

    Join Localytics’ Director of Solutions Engineering Lee Isensee as he details the different key metrics for mobile and web analytics.

    Transcript

    Hi, I’m Lee Isensee, Director of Solutions Engineering here at Localytics and thank you for joining us for today’s Whiteboard Wednesday. Today we’re going to be talking about web versus mobile and, specifically, the different metrics involved.

    We’re going to focus in on three specific topics: base KPIs, user identification and sessions.

    The first thing that we really want to look at is the differences between web and mobile metrics that we typically see. One important element is the mobile world’s concept of users, which is more than just a semantics issue. We’ll come to that a little bit later. In contrast, the web world focuses on the concept of a visitor.

    Mobile sees sessions instead of web visits. Both worlds use events, but whereas websites rely on pageviews, there’s a concept of ‘screens’ in the mobile world which is very different than pageviews. Screens are the frame in which the user is looking at the application, not necessarily the amount of content that they viewed.

    So as we look into this a little bit further beyond those base metrics we have to think ultimately about the user itself. We try to focus on an individual person as they engage with your application or your website, and mobile and web technologies have very different ways of calling them out as individuals.

    In the web world of course we can use very simple methods such as user agent and IP address. Alternatively we can use more sophisticated cookies – first party or third-party – or if your web site has authentication, you can identify users via a login screen or social engagement.

    In the mobile world we actually have fewer options but they tend to be a lot more accurate. In the mobile world we don’t worry about user-agent, IP address and cookies, as we’re able to look at the device itself and get information about it. So whatever mobile device is in the person’s pocket provides us with a general idea that it’s that individual device. As many mobile applications are now taking advantage of social authentication, we can also leverage that to identify a user, and this really helps bridge the gap across additional devices as well. If the person’s engaging with you on the web, social authentication can make the connection between their web usage and their mobile usage.

    Now with all these great opportunities to understand the user there are obviously some down sides that happen from time to time. In the web world we have to worry about roaming users; people who are on their laptops at home, a coffee shop, at work. If you’re using a user agent and IP address method to identify your users, you’re going to get a different one every time.

    Another thing to think about is multiple browsers. In this case, beyond the different user agent, you also have the concern of different cookies.

    Even with an authenticated user, we have to think about the different ways they’re logging in – are we resetting that login? Are we able to persist that?

    Going back to cookies, is your user clearing their cookies regularly? Users can easily remove cookies manually, and some even set up automated, scheduled cookie deletions.

    In the mobile world there are similar issues. As I mentioned a moment ago a person might have multiple devices – multiple mobile phones, perhaps also a tablet. They may also have different setups at home, where they’re sharing devices across users.

    Like clearing cookies, mobile marketers need to be cognizant of users resetting their mobile identifiers. In the iOS world one feature announced with the switch to advertiser ID is the availability for users to reset their device identifier. It is, however, fairly well hidden – certainly less likely for someone to reset a device identifier than resetting a cookie.

    Finally the last thing that we wanted to touch upon is sessions. This is more about how the user engages with your digital assets.

    In the web world we understand some users may come to your website, maybe view a couple pages, get up, grab a coffee – maybe they’re gone for ten, fifteen minutes. They come back, browse a couple more pages. Maybe they open up another tab and go to a different website, then come back.

    Ultimately as long as their browser is pointed at your website within the traditional thirty minute timeout window, all of this activity constitutes a single, perpetual session. You’re left to understand the sequence of those events in the context of one session.

    I like to think of this as a “walk-away metric.” How long did it take the person before they completely walked away from your site?

    For mobile, it’s difficult to really use thirty minutes as that cutoff point. Imagine holding your device in front of you for thirty minutes. That’s really difficult to do for most people and they don’t have that attention span.

    When we think about the experience of the mobile user we have to ask ourselves, “is my application in front of that user, and for how long are they engaging?”

    What Localytics has done, in looking at all of our clients, we found that an appropriate timeout period is not thirty minutes, but rather fifteen seconds. Once a user is out of the application for fifteen seconds, their attention is broken, and their session is over.

    Really, it’s about how users engage with your application. If they get an email do they quickly scroll to the email, view it, and immediately back to your application? Maybe it only took ten seconds and they haven’t lost their train of thought.

    However, if an email comes and they respond to it, that may take them away from your app for a minute, two minutes, five minutes, or more. When they come back to your application, they’ve really lost that train of thought – effectively, they’re starting a new session.

    So these are a couple things that you really want to think about when you’re considering web vs. mobile analytics.

    I’m Lee Isensee, Director of Solutions Engineering here at Localytics, and I’m glad to be able to deliver conversation today about web versus mobile metrics.

  • Best Practices Guide – Mobile Commerce Apps for Retailers

    Share

    Now available for download, this best practice guide provides specific recommendations for retailers who want to leverage native apps for m-commerce to grow mobile revenues and build loyalty. The guide outlines how contextual data and metrics are critical for measuring, tracking and optimizing the mobile brand-customer experiences along every step of the path to purchase.

    In light of the increasing shift in purchase behavior towards mobile, providing an engaging mobile app experience has now become essential to ensure that retailers are engaging with consumers at every step along their path to purchase. The use of native apps lets retailers engage with consumers anywhere and anytime by providing:

    • A key touchpoint for making purchases that can be optimized through rich data on consumer behavior to increase cross-channel engagement and ROI
    • A branded environment to showcase products and the opportunity to reinforce brand consideration at any moment along the path to purchase
    • An effective tool to combat “showrooming” – evaluating an item in-store but deciding to buy it from a competing retailer – by emphasizing the value proposition

    Download the white paper now, and keep up with Localytics’ blog for more best practices, research, and insights into mobile marketing and mobile business strategies that work.

  • Mobile vs. Web Introduction – Whiteboard Wednesday

    Share

    Learn about the different ways to start a mobile strategy, including mobile web, hybrid apps and native apps, and hear Localytics’ Daniel Ruby cover some decision points to help determine which path is right for your business needs in this short informational video.

    Transcript

    Hi, my name’s Dan Ruby and I’m the director of online marketing here Localytics. Welcome to Whiteboard Wednesday. Today we’re going to talk about the difference between web and mobile and to give you a couple of ideas to kick around when deciding what mobile technology is right for your organization.

    You’re all watching this video because you’re already very established, accomplished digital marketers. You’ve been dealing with a website for years, and you’ve watched that website evolve over time from something very basic – maybe a collection of links, a handful of graphics and a call to action – to what is most likely a very rich, interactive branded experience today.

    So the question becomes how do I take this rich, branded experience and port it over to a very small screen that’s in everybody’s pockets now?

    Step number one is to do nothing. As most smartphones have a full HTML-capable browser, they can technically access your existing web site through the browser. The downside of this, obviously, is that the the experience is terrible. There’s a lot of pinching to zoom, scrolling around and a great deal of rich elements that don’t play.

    It works. It’s just not the right way to go.

    Step number two is to make a mobile optimized website. That’s something that your web designers should be able to do off the bat. It’s basically just taking your rich, immersive, interactive website and pulling away a lot of the richness, drilling it down to the core messages and optimizing it for the experience of a small touchscreen.

    This is a really good first active step. It’s a great way to make sure that people who are still coming to your brand via search engines have a mobile experience. It may not be as cool, it may not be as immersive, but it works on a mobile device.

    The next step is to take this mobile web site and wrap it in a native app wrapper. There are several products out there that will allow you to take your existing website, designed to fit in the the mobile framework, and put it into the native language of a particular operating system. You’ve still got an HTML website, but, in the case of iOS, you now have objective C built around it.

    This doesn’t really make much difference in the actual usability of this website, but what it does get you is distribution. Once you wrapped it in this native wrapper you can submit it to one of the various app stores, be it Google Play, Apple’s App Store, Amazon’s App Store and so on.

    The next step is to take the actual usability, richness and experience that your website has evolved to over time and try to mirror that depth of experience on mobile. The way to do that is with a native app – that is, an app that is built from the ground up in whatever language a particular mobile operating system is coded in.

    This allows a lot more interactivity and a lot more cool features. A native app will have full access to a phone’s hardware, so if you’re a retailer for example you have access to the camera, which will allow you to do QR and barcode scanning. If you are a publication it gives you access to the phone’s local storage, which means that you can download your latest issue locally onto somebody’s device – then you don’t have to worry about connectivity. They can read it in a tunnel, on a plane, anywhere.

    The question then becomes “which one of these is right for my business?” You have to decide what levels of depth and interactivity are important to your particular business. Obviously a native app gives you the greatest possible depth of experience, but there are drawbacks to that as well. The biggest is cost: you have to have somebody code a native app specifically for each platform that you want to go to, so if you want to be on Android you have to have somebody who can code Java, if you want to be in iOS you have to have somebody who can code objective C, if you want to be on Windows 8 you need somebody who can code in C Sharp. That will ramp up your development time and your development expenses.

    You have to decide individually whether you want something that is basic, gets a lot of search traffic and doesn’t necessarily need more than fairly simple surface level information. In which case a mobile web site may be all that you need.

    If you want to take that and add on the distribution capability of the app stores, taking that mobile website and wrapping it in a native wrapper, creating what’s called a hybrid app, may be the right decision.

    If, however, you want a really interactive, really rich branded experience, and and you’re willing to to invest the the development time and expenses into it, a native app is probably right for you.

    I hope that’s given you are nice overview of the different possibilities for creating the mobile experience for your brand.

    Again my name is Daniel Ruby and I’m the Director of Online Marketing here at Localytics. I hope you’ve enjoyed this Whiteboard Wednesday, and we’ll see you next week.