Bubble Developer Needed for Google Calendar OAuth (Live App, 100+ Users, Long-Term Potential)
Hi Bubble Community! ![]()
I’m a solo founder who built and launched a Bubble app called Thrive on a Dime, a live coaching and metaphysical services platform designed for self growth and development at a price everyone can afford.
The beta launched on October 1st, and the app is now live with 100+ sign-ups and growing daily. Up until now, I’ve built everything myself, but as the platform scales, I’m looking to bring in an experienced Bubble developer — starting with one well-scoped project — with the hope of continuing the relationship long-term if it’s a great fit.
Initial Project: Google Calendar OAuth & Sync
This is currently the biggest pain point for coaches on the platform.
Goal:
Allow coaches to connect their Google Calendar so their availability inside Thrive on a Dime stays in sync with their external calendar and prevents double bookings.
High-level scope includes:
-
Google OAuth connection
-
Calendar permissions & scopes
-
Reading busy/availability times
-
Preventing double bookings
-
Clean UX for connecting, disconnecting, and re-authentication
Important context:
I’ve already started implementing Google Calendar OAuth in Bubble and got about halfway through (Google Cloud project, OAuth credentials, and initial auth flow). I’m looking for a developer who’s comfortable jumping into an existing app to review what’s been built, complete the remaining logic, and help make it stable and production-ready.
Experience I’m Specifically Looking For
Because Thrive on a Dime is a live app with active users, I’m looking for a developer who has experience beyond MVPs or test apps.
In particular, I’m hoping to work with someone who is comfortable with:
-
Working on live Bubble apps
-
Managing development vs. live versions safely
-
Deploying features to production without disrupting users
-
Collaborating in a multi-developer environment
-
Advising on Bubble plan upgrades and best practices as the app scales
Up until now I’ve worked alone, so I’m looking for someone who can help me adopt clean, professional dev → live workflows as we grow.
Documentation & Knowledge Transfer (Important)
Since I built the app myself, there isn’t formal technical documentation yet. That’s intentional — and part of what I want to improve in this next phase.
I’m not looking for heavy retroactive documentation of everything that already exists. However, it is important to me that I clearly understand how new features are built and how workflows function over time.
For new work, I’d like documentation to be considered part of “done,” such as:
-
Clear explanations of how features are implemented
-
Lightweight written notes or comments for key workflows
-
Loom walkthroughs for complex logic
The goal is long-term maintainability and ensuring I’m never dependent on a single developer.
What Comes Next (If It’s a Good Fit)
If this initial project goes well, I’d love to continue working together on:
-
Outlook calendar sync
-
AI session summaries and onboarding insights
-
Twilio SMS reminders
-
Stripe Connect for coach payments
-
Much more
If You’re Interested
Please reply or DM me with:
-
A brief intro
-
Your Bubble experience (especially live apps)
-
Any OAuth / API work you’ve done
-
Examples of apps you’ve worked on
-
Your availability and preferred engagement style
Here is a forum post for more info about the app and my Bubble journey.
Thanks so much for reading — I’m excited to find someone from this community to collaborate with and help take Thrive on a Dime to the next level ![]()
Warmly,
Laura