Cloning Your App for a Customized Sales Experience
Why one-app-per-user is better than one-app-for-all
App cloning means creating versions of an app or mobile website where each user has a different URL. It is one of the most useful and unique capabilities of the Tapps platform.
The most common reasons for app cloning are:
Lower onboarding friction
Similar to most websites, traditional native apps operate on the one-app-for-all model. To generate unique information for each individual, they require a login or rely on cookies. Tapps provides an alternative model of one-app-per-user or per-event without the friction of creating a login and without invasive cookies.
Discover some of the most common ways Tapps customers use app cloning:
Digital business cards are a simple, yet powerful, example. Once a company has selected the content to include on its digital cards, it can copy the template to a unique app for each employee, while still maintaining the ability to customize individual information, such as contact information or photos.
Tapps also provides robust tools for managing common content in one place, so if each digital card includes the company address, then an update to the address in the template will instantly update all the digital cards. The metrics for interactions with common content are individually compiled for each app for full visibility into the data.
Another common use case is when a digital brochure is issued for each individual salesperson or agent. Sales made through the app can be attributed instantly to the person making the sale. See how Pixlrabbit, a web design agency in Atlanta, is using their digital brochure here.
Another example is a digital drug card. A user can carry a paper discount drug card in their wallet, but it is more convenient to carry that card digitally as an icon on their phone. Not only is a digital app more accessible, but it also can help find which nearby pharmacy has the lowest price. This digital drug card app was built on the Tapps platform.
Each digital drug card is unique to the individual and carries a different card number which increases privacy. Different from a native app for drug cards, which requires an email address and login, the digital card can uniquely serve the user without ever capturing any personal information, and yet it can still deliver individual activity metrics. This approach also reduces onboarding friction because it eliminates the need for user login to quickly access the information.
In the above examples, each of the cloned apps contains slightly different content.
A case for cloning where all the apps might have identical content is connected packaging, which is a one-app-per-item use case.
Each product might have a QR code on its packaging that displays a product guide (like this sample app) or a bundle of information such as a manual, support link, quick-start video, FAQs, accessories purchase link, etc.
You may need unique metric tracking for each item. You can capture metrics telling you which piece of information had the most interactions. You can even tie the unique item URL to the product serial number, manufacture date, etc. This gives you the ability to track advanced, targeted metrics about how customers interact with your information.
Consider the use case for a conference or training event that is repeated in multiple locations and on different dates throughout the year. An individual event app can contain common content (e.g. agenda, what to bring, promo video, etc.) and also information unique to each event (e.g. location map, registration link, etc.).
Not only is the individual event app helpful to attendees, but it becomes a very useful marketing tool for each event. Registrants can share the app in their local social channels to recruit attendees for future events.
One-app-per-channel or campaign
App cloning provides a powerful marketing tool. When you share a link in different channels (e.g. Twitter vs. Linkedin), creating a different version for each channel allows one to independently measure the performance of the channels. Because the actions are shared between these apps, content updated in one place will update all the apps, though each may have content unique to a channel or campaign.
The good news is: you don’t have to clone these apps one by one. For large-scale deployments, Tapps enables you to build and manage apps via a GraphQL API, so everything can be done programmatically.
With Tapps, you have the ability to create custom apps and replicate them at scale. Now you can maximize engagement while offering a personalized experience for your users.
What will you create?