Conclusion

When I started building Praport, the idea was simple: create a better shipment tracking experience — something faster, cleaner, and more focused than the legacy tools I had used in the logistics industry.

That initial idea grew into a real product. From a barebones HTML version with local database support to a fully integrated full-stack application with React, Supabase, and Express — the progress was substantial. Along the way, I learned how interfaces are built, how state is managed, how servers run, and how data flows between systems.

Version 1 helped validate the concept. It was basic, yes — but functional and honest. Version 2 took the next step, introducing a modern tech stack, proper authentication, deployment flows, and frontend logic that was scalable and more polished.

But despite the progress, it became clear that building, maintaining, and scaling a product like this required far more than just part-time effort of person with limited exposure to progamming and speciality of business major. Debugging, learning new libraries, API issues, styling adjustments, database logic, version control — all that veered me into software developer path, which was not my preferred vision.

And that time often came at the expense of something equally, or more important: the business side. Customer acquisition, strategy, outreach, onboarding, pricing, and positioning didn’t receive the attention they needed. Instead of using code as a tool to grow a product, coding became the product.

The reality is — I started this journey with limited programming experience. And although I’ve grown tremendously from it, I also realized that continuing development would require a full-time development commitment. That’s not the role I set out to take in this venture.

So this is where the project pauses. Not because the idea failed, but because the path forward demands a focus that no longer aligns with my core strengths and priorities.