Inspiration
In many African communities, traditional healing is the first point of care—but finding a healer is still largely offline and based on word of mouth. Most healers who want to be accessible operate informally—sharing their services in Facebook groups, relying on referrals, and lacking tools to manage patients or build credibility online.
Native Heal was inspired by the need to make accessing traditional healers safer, more transparent, and more convenient—preserving cultural heritage while embracing modern technology.
What it does
Native Heal is a digital platform with features including:
- Search & request: Patients can search for traditional healers and request to book their services.
- Messaging: Secure in-platform communication between patients and healers.
- Ratings: After a consultation, patients can rate and review the healer, helping others make informed decisions.
- Blogs & events: Users can read and share culturally relevant blog posts and discover upcoming community events.
How we built it
We built Native Heal using Bolt, with Supabase powering the backend. Development was done almost entirely through AI prompting with ChatGPT, which allowed me—coming from a non-technical background—to build a fully functional product using nothing but prompts. Every part of this platform, from UI to data structure, was created directly in Bolt.
Challenges we ran into
This project was rebuilt three times.
- The first version crashed due to scale.
- The second version was accidentally deleted when trying to reduce token usage—I hadn’t connected it to GitHub.
- On the third try, I started from scratch and got to the final version.
Later, we faced major issues when we switched to a production database. We didn’t realize the RLS policies and table structures were different from our test environment, which broke the app. The more we prompted Bolt to fix things, the more it edited the code to suit the broken structure—making it worse. Eventually, we reverted back to the original database, which was also unstable by then. But we kept going.
Accomplishments we're proud of
We’re proud that despite all the setbacks, we were able to build a fully functional product in under a month. It works, it reflects the original vision, and it was created entirely by a solo founder with no coding background—powered by Bolt, ChatGPT, and a whole lot of persistence.
What we learned
- Prompts are everything. Precise prompts = better results.
- Think like a product manager: plan your data structure, auth flow, and UI.
- Connect to GitHub and Supabase early—this helps ChatGPT work better with your actual schema.
- Bolt doesn't always refactor your code, but you can prompt it to clean up or organize code—this saves tokens and improves maintainability.
- Use discussion mode to clarify logic when unsure.
- Run cleanups—they really help, especially as your app grows.
What’s next for Native Heal
We’re just getting started. Next steps include:
- Integrating Twilio SMS to send appointment notifications.
- Marketing and onboarding early users before introducing payment features.
- Reaching 1,000 healers, then building and launching the mobile app on the Google Play Store.
- Continuously iterating based on feedback to improve user experience.
Native Heal is a deeply personal and culturally relevant product. Thanks to Bolt, it exists—and it's only the beginning. Please note: admin test details : admin@nativeheal.co.za password: Melania@2025 admin has to approve the healer for them to appear on the website to be booked.
Built With
- bolt
Log in or sign up for Devpost to join the conversation.