Skip to main content

From Bedside to Build - How a Priset Engineer Solved a Real-World Hospital Bottleneck

· 5 min read
Priset AI
Priset AI
The AI Engineering Partner

How a Priset Engineer Solved a Real-World Hospital Bottleneck By a Lead Engineer at Priset

Even working at Priset, I held a firm belief: "Vibe coding is only good for prototypes."

As an architect, I've tested plenty of AI coding tools. My verdict was always the same: great for small functions, but for a production-grade application, the manual verification and "interviewing" of the AI takes more effort than just writing the code yourself.

But yesterday, a personal problem forced me to challenge that belief. The result? I built a complex, production-ready React Native and .NET 9 application in a single day, using the very tool I help build.

Here is how I went from an idea to a potential App Store submission in 24 hours, with zero prior experience in mobile development.

The Problem: A Doctor's Burnout and a Broken Process​

It started when my wife, a doctor, came home late, frustrated by the inefficient administrative processes at her hospital. She described how patient notes, a critical but tedious task, were creating bottlenecks. These delays didn't just cause physician burnout; in some cases, they forced patients to stay in the hospital an extra day simply because their reports weren't finalized.

As she vented, my architect brain kicked in: We could automate this.

I envisioned an app that would streamline her workflow, allowing her (and other doctors) to finish work on time. But I didn't want a toy prototype. I wanted a deployable, secure, commercial-grade application that I could potentially monetize.

The Challenge: A Production-Grade App with Zero Mobile Experience​

I set a high bar for the requirements:

  • Mobile App: React Native (for both iOS & Android)
  • Backend: ASP.NET Core 9
  • Web Portal: A separate viewing interface for administrative tasks
  • Authentication: A complex QR code "WhatsApp Web" style login for security and ease of use.

The catch? I had never written a single line of React Native code in my life. For most developers, setting up the environment alone would take days. This was the ultimate stress test for my own product.

The Process: A 24-Hour Journey from Prompt to Product​

I decided to put Priset to the ultimate test. I didn't write a technical specification document. Instead, I provided a half-page, high-level requirement list and asked for the full stack setup. Honestly, I was expecting it to fail.

Phase 1: The "Impossible" Setup (~30 Minutes)​

In half an hour, Priset didn't just write code; it acted as my expert DevOps engineer.

  • It scaffolded the React Native app.
  • It set up the ASP.NET Core 9 backend.
  • It installed all necessary Libraries and NuGet packages.
  • It handled the environment configurations.

When I ran the code on a mobile emulator, it just worked. No dependency hell, no version conflicts. For a technology I didn't know, this was magic.

Phase 2: The Collaborative "Vibe" Loop​

Was the first draft perfect? No. But it was a fully functional foundation. This is where the true power of the "developer as director" workflow shined.

I realized my initial prompt lacked clarity on certain business logic, so I treated Priset like a senior developer who works at light speed. I gave it conversational feedback: "Change this," "Handle this edge case," "Fix this flow."

Priset didn't complain. It iterated instantly.

  • Integrations: It implemented Google & Apple Auth, Payment Gateways (for potential monetization), and AI integrations (Gemini for note summarization) seamlessly.
  • The "WhatsApp" Feature: I requested the web-login feature where the mobile app scans a QR code on the browser. I had no idea how to build this. Priset nailed it on the first attempt.

The Outcome: A $100k Project for the Price of Dinner​

Within one day (including rest time), I had a fully tested application running on my local device, handling payments, AI requests, and secure authentication. I am now preparing to submit it to the app stores.

The economics of this project shocked me:

  • Total Time: 1 Day
  • Priset Credits Used: ~3,700
  • Total Cost: ~$230 USD

If I were to hire a dev team or bill my own hours for a project of this complexity, it would easily be a $100,000 engagement spanning many months. I achieved the same result for the price of a nice dinner.

But the real validation came from my wife. After her first day using the app, she told me, "This is the first time in months I've finished my notes before my shift ended. You didn't just build an app; you gave me back my evening."

Conclusion: Our Mission in Action​

Is Priset 100% autonomous? No. And as the developer, I didn't want it to be. I wanted control over the direction while the AI handled the flawless implementation.

This project was personal, but it's the perfect embodiment of our mission. It proved that deep domain knowledge is no longer a barrier to entry. As an architect with no mobile skills, I built a mobile business. Priset didn't just save me time; it empowered me to bring a startup idea to life without a co-founder or a dev team.

If you are sitting on an idea because you "don't have the resources" or "don't know the language," those excuses represent the old world. In the new world, all you need is a vision.

This is why we're building Priset. We're not just building a tool; we're building an engine for innovation.