Overview
Welcome to Custom Screens, here's what you need to know
You are viewing SDK Version 1.10
This documentation covers the complete set of capabilities for Version 1.7 of Tapcart's underlying Web Bridge SDK. This SDK is the backbone that connects your solutions to native mobile apps.
What are Custom Screens?
Custom Screens allow you to bring one of a kind & immersive eCommerce experiences to Tapcart apps. This could be anything from a subscriptions management page, to a blog, to an order tracking page. Following the concept of Custom Blocks, Custom Screens can be fully customizable and built to integrate with the Web Bridge SDK so that it can interface with the native mobile app.
How are Custom Screens built?
Custom Screens are built & implemented on your own external web application. This could be a new react app you've spun up, or a liquid site that you already use as your primary website. They can be built in your IDE or choice, deployed through services of choice, and are also compatible with Hydrogen/Oxygen. Building a Custom Screen is a technical project, and should be led by a web developer.
What can be accomplished with a Custom Screen?
Custom Screens can be used across a wide spectrum of use cases. At the end of the day, they make the most sense when used for experiences that should take up the entire page that the user is looking at. The most common delineator for why you should use a Custom Block vs Custom Page comes down to how immersive the experience is, as well as if your aim is to share code between the website & the app. While this is far from an exhaustive list, Custom Screens can be used to pursue implementations of:
- Loyalty
- Subscription Management
- Order Tracking
- Blogs
- Look Books
- Custom PDPs
and the list goes on...
Helpful links
New to screen building?
Looking for available Variables?
Looking for available App Actions?
Are you a Tapcart agency or technology partner?
Updated about 2 months ago