ePine

• 

• 

  Architecture and Technologies

ePine is a platform where you can find diverse services for diverse needs anywhere in the world. The platform, besides searching for services, provides an easier and unique experience to book, see details and cancel the appointments that you can create by choosing the best option for you.

Inspiration

The idea came quite natural because I am always searching for services like sport, beauty or other and it's quite difficult to keep the list of the appointments since every business has it's own method to book a service. So, I thought that this may become an opportunity to implement a solution for this issue and create a place where everybody can find and book services.

What it does

The platform has implemented the following functionalities:

• Account management: register, login, logout, etc.
• Search for services (merchants) - using
• See details of a service (using Locations API, TeamMembers API, Catalog API)
• Create a booking (using Locations API, TeamMembers API, Catalog API, Bookings API, Customer API)
• See list of the appointments created
• See details of an appointment (Booking API)
• Cancel a booking (Bookings API)
• Dashboard - see appointments
• Onboard a new merchant

How we built it

From the architecture point of view, here you will find the diagram that explains how the solution was structured. The platform is created using:

• a Server Blazor application (.Net 6.0) that connects to a database and to the Square API
• a SQL Server database where minimal information about users, merchants and appointments is kept

Challenges we ran into

Since it was the first time when I used the Square API, I needed some more time to understand the platform, to understand the data provided by the API and how to manipulate it. A major challenge was to make the Bookings API working because with the free plan I didn't had rights to create a booking. I updated to the premium plan and I manage to make it work.

Accomplishments that we're proud of

Over all, a big accomplishment is the project itself. I am really happy to see my ideas implemented and being used. A second accomplishment is that I understood the Square platform and the API, managing to use them in creating the business logic of the platform.

What we learned

Here I can mention all the Square APIs used: Bookings API, Catalog API, Customer API, Locations API, TeamMembers API. More that that, I learned how to use the Square platform from the seller point of view.

What's next for ePine

ePine dreams to be personal assistant of a person from the appointments point of view, so new functionalities can be very useful and also some improvements for the existing functionalities will be very appreciated. Some examples of new functionalities:

• add more options for the bookings
• contact seller directly from the application
• reviews for the services and the team members
• pay in the application while booking the service using Square API
• etc.

Built With

• .net6.0
• appservice
• azure
• blazor
• serverblazor
• sqlserver
• square-bookings-api
• square-catalog-api
• square-customers-api
• square-locations-api
• square-teammembers-api