Pocket Promoter: Case Study

📑 General Info About The Project

Here are the general characteristics of this project:

Let’s switch to core features of the Pocket Promoter app and discover how we managed to implement them!

😍 The Most Memorable Features

Since the app is aimed at musicians and event planners at the same time, it has 2 workflows depending on who you are and what you’re looking for. Let’s review them both!

Event Planner’s Workflow 👩‍💼

After entering the app, users are offered to Sign Up as a regular user or an artist. As for now, we’ll stick with the first option.

This is a must-do step since it allows to get all the necessary information for the further use of the application. Why do we ask users to sign up?

As always, we’re also happy to share with you our development toolkit that helped us to deliver this application for both platforms in the shortest time.

⚙️ Tech Stack

Before we tell you how we managed to avoid designing a BackEnd, let’s check out which tools we used to build the React Native MVP:

When working on this project, we decided to avoid the BackEnd side and replace it with a serverless solution. Our motivation was simple:

1. We wanted to get away from boilerplate (code that is duplicated many times).
2. We wanted to avoid designing APIs for every request.

For this purpose, we used Firebase products. It allowed us to make the app work with the remote database in the way as it is local. That means that the Pocket Promoter application has no BackEnd side but still runs without any losses in performance.

Beside that, when our client will be scaling – the selected tech stack will allow him to do that without additional work.

Actually, Firebase products are a generalization of the frequently used parts of any BackEnd.

💻 Prototype

Finally, we would like to show you an interactive prototype of the Pocket Promoter app. Feel free to explore it on your own!

**