Photo by Nick Fewings on Unsplash

#001 First Week

20. Mar 2021

HELLO ...

It has been about a week now since I went public with Itsy last Sunday with a post on LinkedIn. More of you have signed up for this email update than I anticipated, and for that I am very thankful. Building this in public means these emails will be published on the itsy.so website in the coming days, so that everyone can see how it started, and how it's going.

SO FAR ...

The main sales widget is at an MVP level. It's able to display the products on the page, calculate prices, check for availability, collect participant and client information and create a new order in the system with all the relevant bookings. Payment functionality is still undecided. Should I handle them internally through APIs, or should I send users to a payment page/link? If you have opinions, tell me!

As I wrote on IndieHackers, the tech stack is pretty much decided, with Google Cloud Platform the main option I selected for hosting and data storage.

As you can see from the stats below (which will grow over time), I made 39 code commits this week. I am still figuring out where to put some things, but basic functionality and setup is already there.

SO NEXT ...

Next week I want to start on the backoffice application, where user can log into their workspaces, create Trips, manage Orders and configure all the planned Integrations. I have some structure for the internal api already, and some idea on how to build out the application (using Vue).

I am thinking a lot about what words to use for things in the Itsy System, should the main entity be called a Package or a Trip? Is it a Participant or a Passenger? If you have any particular view on that, please let me know!

STATS ...

  • Code commits: 39 (105 total from 5th of Feb)

LINKS ...

Back Home More Updates