What happens when an app loses its connection, signs you out or loses your data on update, and what to build first. By Bogdan Vladoiu.
By Bogdan Vladoiu, 2023-07-20
Key factors contributing to this drastic drop-off are lack of robust offline functionality, a feature that can make or break a modern mobile app, and no support to be shared upon release.
The Importance of Offline Functionality
In an increasingly connected world, one might question the importance of offline functionality. After all, isn’t almost everyone always online? The reality is a bit different. Users can sometimes find themselves in situations where they don’t have access to a reliable internet connection, but that is not the point!
When an app doesn’t work offline or doesn’t even show data offline, it can give users the impression that the app is unreliable or poorly designed.
The Good, the Bad, and the Ugly
Let’s take a look at a couple of examples and try to better understand our user.
Gmail: Google’s popular email client is an excellent example of an app that provides a seamless offline experience.
Put your phone in flight mode. Open Gmail. Try to delete some emails. Try to compose some drafts. Would YOU use a different email client app that sometimes doesn’t show your emails? Do you have to be on a flight to decide or did you already make up your mind to use this app?
Revolut: This digital banking app also allows users to, amongst other things, check their balance offline.
Put your phone in flight mode. Open Revolut. Can you see your balance? Would you use an app in which you cannot see it? Do you have to go camping with no signal for a weekend to make this choice or have you already decided?
These examples clearly show that the absence of reliable offline functionality can be a deal-breaker for many users. And users get a little anxious at the thought of being locked out of their data way before it actually happens! They put up with this a few times if they don’t have a choice. But the second a similar app pops up that works offline, they jump over without failure.
Don’t Lose Users to Poor Connectivity
While offline functionality might not be the entire story when it comes to user retention, its definitely disproportionately valued in poor/flaky connectivity situations that users always remember. Don’t lose users to poor connectivity — this is a mantra that every app developer should take to heart. It’s a disastrous scenario for any business, and the worst part is that it’s entirely avoidable.
The notion that some apps can’t provide offline functionality due to their nature or the amount of data they handle is a simply not true. There is ALWAYS some functionality that can be implemented offline. Let’s take the example of an e-commerce app, where users browse through numerous products and make purchases.
You might think, “How can an app like this function offline when it needs a continuous internet connection to update product listings and process transactions?” Here’s the thing — you don’t need to cache all the data. Focus on critical data, such as the user’s past purchases or favorited items. Why?
You can ALWAYS make a deal with your user offline!
And sometimes it’s all it takes to be the winner in your market. Especially if your competitors’ apps don’t offer any offline functionality.
Imagine a user who opens your app while offline, perhaps during a flight or in a location with poor connectivity. If your app refuses to function without an internet connection, the user is going to put their phone back in their pocket and move on. But what if they later walk into a store to buy what they wanted? That store might still not be yours, and the sale you could have made through your app goes to someone else.
Now consider a different scenario. The same user opens your app while offline. But instead of a blank screen or an error message, they see their previous purchases and a ‘repurchase’ button. They can click this button to schedule a repurchase, and the app reassures them: “You are offline, but we can schedule this purchase as soon as a connection is restored.” You may even simplify the message. When I tap the Send email button in Gmail, offline, it just says “This email will be sent later”. And after I tap it I just allow myself to forget about that email! This is how this app empowers users!!
Getting back to our e-commerce app example, for all practical purposes, you’ve just made a new deal with that user, offline. With a bit of creative thinking and a user-centric approach, you’ve turned a potential user drop-off point into an opportunity for engagement and sales.
Remember, the users who open your app while offline aren’t doing so out of boredom. These are users who are invested in your app, who find value in what your app offers to the point where they want to use it even when they can’t connect to the internet. These are often your most valuable users, and providing them with a seamless offline experience is key to keeping them around.
By focusing on offline functionality, not only can you retain your existing users, but you also have a golden opportunity to attract users from competitors whose apps don’t work offline. It’s a win-win situation.
Streaming Apps: A Case for Offline Functionality
At first glance, it might seem like there’s no room for offline functionality in a video streaming app. After all, you can’t stream videos without an internet connection, right? But let’s look a little deeper.
Imagine a user who has three video streaming apps installed on their phone. One day, a friend recommends a show to them — let’s say it’s “The Witcher.” The user recalls seeing this show on the homepage of one of their streaming apps, but they are currently offline and can’t stream the show right away.
However, if the app has been designed with some offline functionality in mind (caching show thumbnail and title, and not a thing more), the user can still open the app, search for “The Witcher,” and add it to their favorites or to a “watch later” list. This user can go on and completely forget he did this (and they do) and the conversation he had (and I do). Some time later once they’re back online, they see the show in their watchlist and stream it.
In this scenario, the app has provided valuable functionality to the user, even without an internet connection. And if the other two streaming apps on the user’s phone don’t provide this kind of offline functionality, they will likely lose out to the app that does.
This is a compelling example of how offline functionality can make a difference, even in apps where the primary function relies on an internet connection. By providing some level of offline functionality, you can keep users engaged with your app and stay ahead of the competition. Over time, as users come to appreciate the added convenience and functionality, competitor apps that don’t work offline will gradually lose users to your app.
Industry Trends
The mobile app industry has come a long way in the past decade. As user expectations continue to rise, offline functionality is becoming less of a luxury and more of a necessity. With the advent of Progressive Web Apps (PWAs) and other technologies, even web apps are now expected to provide some level of offline functionality.
While implementing robust offline functionality can be challenging, the potential rewards in terms of user retention and satisfaction make it an investment worth considering for any app developer. In the increasingly competitive mobile app market, providing a seamless offline experience could be the key to standing out from the crowd and ensuring the long-term success of your app.
If I didn’t make you tap out already, remember, even in an app where the main functionality requires internet, there are ALWAYS auxiliary features that can be made to work offline. The key is to identify these features and implement them well.
Avoiding Unnecessary Login Screens and Data Loss
A common mistake many apps make is slamming a login screen in the user’s face as soon as they open the app. While user authentication is essential for certain app functionalities, requiring the user to login just to open the app for the first time, is simply, right then and there, the end of the journey.
Consider the example of e-commerce apps. Many of them allow users to browse products, read reviews, and check prices without needing to log in. This is because these apps expose some public API endpoints that don’t require authentication. Users are only asked to log in when they’re ready to make a purchase or leave a review. This approach allows users to explore the app and see its value before committing to create an account or log in, leading to a better user experience and drastically higher conversion rates.
The same principle applies to video-on-demand services. Most of these platforms allow users to browse their catalog and see what shows and movies are available before asking them to log in or sign up.
Another factor that contributes to the high user drop-off rate is not keeping users logged in indefinitely. Logging out should always be an intentional action taken by the user, not something that happens unpredictably. For example, Gmail keeps users logged in forever, requiring re-authentication only in specific circumstances, such as when the user is attempting to change their account settings.
Unfortunately, many apps don’t prioritize implementing background token refresh, which leads to users being logged out unexpectedly. This can be highly frustrating for users and can lead to decreased user engagement and retention.
Similarly, a lot of developers take the easy route when it comes to data management. Instead of implementing proper schema migrations, they simply delete all tables and create new ones when the app updates. This approach results in users losing their data, which can be a major blow to the user’s trust in the app and can lead to users uninstalling the app.
As a developer, it’s crucial to understand the negative impact of these practices on user retention. Take your developer hat off. Be a user. Would you put up with this?
The best way to never lose a user is to never throw him out of the app, under any circumstance.
And it can be more difficult to implement these features further down the road, and some users may have already left!
For how this is built, from background token refresh to migrations that never lose a row, see Maximizing user retention.
Harnessing the Power of Deep-Linking
In today’s interconnected digital world, apps don’t exist in isolation. They’re part of a broader ecosystem where users are constantly networking and sharing through various channels, be it chat, SMS, or social media. Deep-linking is a powerful out-of-the-box feature that can allow your app to tap into these free ecosystems and propagate seamlessly.
Consider a food delivery app that allows users to browse menus from various restaurants and order meals. A user has just discovered a delicious dish from a local restaurant and wants to share this find with their friends. With deep-linking, they can generate a link for that specific dish and share it through their preferred channel, be it a chat app, SMS, or social media.
When their friends click on the link, if they haven’t installed the app, their Android phone will automatically offer to install it for them. Once installed, the app opens straight to the dish, providing a seamless experience for the new user.
This is not just about sharing data; it’s also about sharing the app itself. It’s a free, seamless, and highly effective way of promoting your app. When users share content from your app, they’re not just recommending that content; they’re recommending your app.
Unfortunately, many developers overlook the potential of deep-linking or consider it much later. This is a missed opportunity. There’s always some type of data or functionality that users would find valuable and worth sharing. This should also be a top priority, for the initial release of an app, rather than sitting on this feature for 3, 4, 6 months, time in which some users might leave.
I’ve seen some teams implement in their applications’ early releases, deep-links for resetting passwords or activating user accounts. But no deep-links for data sharing. This may not be the best idea! Unless it’s a necessity, i.e. no client has account/password management capabilities, including the web app, then sure, the links generated in user email responses by the user account back-end component can be leveraged directly in the client apps via deep-linking! But assuming this is taken care off in the web app, your top priority should be sharing the app, i.e. developing the deep-links to data/features in the app most valuable or appealing, and therefore most likely to also share the app!
By implementing deep-linking, you’re not just improving the user experience; you’re turning your users into ambassadors for your app, for free, out-of-the-box. It’s such a big win. Regardless of the nature of your app, be like that food app and enable some data sharing from release 0.
For a more in-depth guide on deep links, including what really happens today on a phone that does not have the app yet, as well as other tips for bringing users in, check out Maximizing user acquisition.