Boat Passport pre-launches to early testers

I've been building an app called Boat Passport for the last month. Yesterday, I felt the MVP was solid enough to share with a group of early testers to get some feedback and see if it gains traction.

What exactly is this app? Every boat owner, especially sailboat owners, faces a lot of maintenance and breakdowns during their boat's lifetime. After all, there's even a saying, *"BOAT: Break Out Another Thousand"*. To keep track of all of the above, plus insurance, safety equipment, first aid kit, etc., most resort to a collection of spreadsheets and notebooks. This can work out for a while until the sheer volume of records makes one wonder if he has taken on a part-time job as an accountant, a poor one at that. With the worst-case scenario being the loss of such records due to either the elements of the sea or the little gremlins hidden inside each spreadsheet that catalyse the shedding of one's hair. Lucklily, I've created a tailor-made solution to the problem, something that, has far as I know, was not yet available.

Key features include:

• Maintenance: Divided into recurring maintenance logs, based of templates, so that everything can be backtracked, and Repairs one-time jobs that don't follow a template.
• Inventory: Divided into Safety Equipment, Spare Parts, and First Aid Kit.
• Smart reminders: Automatically generated based on maintenance templates (last recorded maintenance date) and inventory expiry dates. These can only be cleared by updating or deleting their source. This ensures that reminders are always up-to-date, low-maintenance, and tied directly to the source data, requiring no manual cleanup.
• Analytics: For now, only expense tracking and categorization. Maintenance expenses recorded in "Maintenance" get automatically synced here.
• Voyages: Simple manual voyage tracking.

This tailor-made solution makes logging and keeping up with all the urgent deadlines a breeze. It's currently at an MVP stage. I have lists of features that would be cool to implement, but I'm refraning from doing so, betting that the user knows best what's missing. For now, only early testers can influence which new features get added and their place on the implementation schedule. If you want to keep up with the progress, refer to my now page.

I'm really excited about the progress I've made so far. It was a very intense month of coding and debugging. It's genuinely fun when you are learning and challenging yourself to do something you're passionate about. Exciting things lie ahead if I keep up this pace. One small bet has been placed, with others to come.