Overview — Screens, Database, Layout Settings, Use Cases
This template allows users to browse categories of events, choose an event, and purchase tickets. Admins can create and manage events and see a dashboard of purchase activity.
The Browse, Purchase, and Manage Events Feature Template is the perfect addition to your app if you’re looking for a way to sell tickets or registrations for events, workshops, or experiences. Each screen is designed for an optimal user experience to not only make the purchase of your tickets or registrations easy, but also the management and creation of those events.
Included Screens:
User Screens
These screens will be interacted with by the attendees or clients of your app.
📚 Instructions Screen
Quickly get an overview of the template with quick tips, a help doc, and associated templates that may be of interest. This screen may be deleted at any time.
📝 Category List Screen
This screen contains an image, title, description, and list of categories that your events or experiences may be divided into.
📔 Events List Screen
Dive into events offered within a category. This screen comes with a customizable breadcrumb navigation for your users & a custom list.
🔎 Event Details Screen
View all information related to your event on the Event Details Screen. From location, time, and availability to price, images, and more — this screen holds it all!
💰 Purchase Screen
Set up your Stripe account to seamlessly manage the purchase process for your end users.
✅ Congrats Screen
Inform your users when they have successfully made a purchase.
Admin Screens
Admin Screens are accessible to users who have permission to view and interact with those screens.
👩🏾💻 Admin Manage Events Screen
Review available events or workshops offered from this screen with options to add, edit, or delete each offering.
🏦 Admin Transactions Screen
Review and monitor all transactions in a dashboard view with associated table of data.
⚒️ Admin Create Event Screen
Add an event to the roster or workshop offerings. This is where an Admin will create new events to offer in the app.
🔄 Admin Edit Event Screen
Update an existing event or workshop through the Admin Edit Event Screen.
Database
The Browse, Purchase, and Manage Events Feature Template comes with a database that contains sample data. Each Adalo database contains Collections, each with the associated Properties. Any necessary relationship between the collections is set up, as well.
Below is an outline of the included Collections and their Properties. The Collection name is bolded and includes a description. The Properties include their name, property type (in brackets), and a description.
Basic Collections & Properties:
👥 Users
The Users Collection automatically comes with every Adalo app. This collection will hold all the information related to anyone who uses the app. This information is initially collected from users when they sign up to use your app.
Email [Text] — The user’s email address. Created upon sign-up.
Password [Encrypted Text] — The user’s password. Created upon sign-up.
Username [Text] — The user’s username. Created upon sign-up.
Full Name [Text] — The user’s name. Created upon sign-up.
Transactions [Many-to-One Relationship] — A relational field between users & their transactions. Each user can have many transactions; however, a unique transaction can only belong to one user.
Profile Photo [Image] — An image of the user. Created upon sign-up.
Admin? [True / False] — A property to recognize the user's permissions. If the user is meant to be an Admin, this property should be set to true and is denoted with a checkmark in the interface.
🗓️ Events
The Events Collection holds information related to the events you offer. This information can be added through the Adalo interface (manually or via .csv upload) or from the “Admin Create Event” or “Admin Edit Event” screens.
Name [Text] — The title of the event. This is how you externally refer to the event.
Primary Image [Image] — An image you want to display for the event.
Category [Many-to-One Relationship] — The category/categories an event belongs to. This is a relational property where many events can belong to one category; however, each event can only have one category.
Short Description [Text] — A brief description of the event. Typically, one sentence.
Long Description [Text] — A longer, more in-depth event description. Include all pertinent details.
Starting Time [Date & Time] — The day and time the event begins.
Ending Time [Date & Time] — The day and time the event ends.
Total Time [Number] — The number of hours each individual event lasts.
Location [Text] — Where the event will take place.
Price [Number] — The cost of the event.
Total Possible Spots [Number] — The number of people who can register for the event.
Available Spots Remaining [Number] — The total spots remaining for registering for the event. To begin, this number should match the ‘Total Possible Spots’ value.
Transactions [Many-to-One Relationship] — These are the transactions tied to the event. This is a relational field where many transactions belong to one event, and each transaction is unique that event.
Publicly Available? [True / False] — A property to recognize if the event should be visible to customers. If the event should be visible, then this property should be set to TRUE; if it should not be available, the property should be set to FALSE.
🏀 Teams
This template is sports-themed so this Collection holds team information. If you have events without teams, you can use this to hold other types of group information.
Name [Text] — The name of the team
Short description [Text] — A brief summary of the team
Long description [Text] — A longer description of the team
Games [One-to-Many Relationship] — This ties teams to events. One team can have many events.
💰 Transactions
The Transactions Collection holds information regarding any purchases made. This information is created once a user completes the process on the “Purchase” Screen.
Name [Text] — The name given to the transaction. Upon first download of the template, the name is populated in the following format: Full Name of the User — Name of the Event
Status [Text] — The outcome of the transaction.
Purchased Event [One-to-Many Relationship] — A relational field to display which event was purchased where one transaction purchases one event; however, one event can have many transactions.
Purchased by User [One-to-Many Relationship] — A relational field to display which user purchased a event where one user purchases one event; however, one event has several users.
Cost [Number] — The price of the event.
Layout Settings
Each screen in the Browse, Purchase, and Manage Feature Template is created using a responsive design. The screens will look good on any device or tablet.
Most screens have been designed with Custom Layouts. If you add a new component to a screen, you might notice that the other screen sizes are impacted.
Layout Overview:
To view or edit the layout for different screen sizes — click the Screen title to reveal the dropdown.
The default view for this template is Desktop. When you change the screen size for one screen in the Builder, it does not change the screen size of the rest of the screens on the canvas.
Hidden Components
In each view, there may be components that do not appear on Desktop, but are visible on Mobile. These are grayed out in the lefthand panel & denoted with an icon.
Another way to view which device components are visible is the Layout Tab here:
Custom Layout
Some components come with custom layouts based on screen size. To view those settings, check the Layout Tab & scroll to the Custom Layout Settings.
Example Use Cases:
A conference organizer who sells tickets for multiple keynote sessions and workshops.
A music festival that offers passes for various performance days and VIP experiences.
A workshop facilitator who sells spots for hands-on learning sessions in different crafts or skills.
A sports organization that offers registration for tournaments or training camps.
and many more!
Last updated
Was this helpful?
