GMB Booking is still in test mode, and I'm at a crossroads. Got a ton of feature ideas but limited time before launch. Need your developer brain to help me prioritize what actually matters vs what's just feature bloat.
The Feature Dilemma 🤯
Classic developer problem: I keep thinking of "cool features" but I need to focus on what users actually want. Help me separate the must-haves from the nice-to-haves!
Current MVP Features ✅
What's already built:
- Basic booking calendar
- Payment integration (Razorpay)
- Email confirmations
- Simple business dashboard
- Mobile responsive design
Feature Ideas I'm Considering 💡
Integrations:
- WhatsApp booking confirmations
- Google Calendar 2-way sync
- Zoom meeting auto-generation
- SMS reminders via Twilio
Business Features:
- Multi-location support
- Staff scheduling management
- Custom booking forms
- Analytics dashboard
- Customer database/CRM
User Experience:
- Booking widget for websites
- Social media booking buttons
- Waitlist management
- Group/bulk bookings
- Recurring appointment setup
Technical Enhancements:
- API for third-party integrations
- White-label solution
- Multi-language support
- Offline booking capability
Test The Current Version 🔗
Platform: https://gmbbooking.netlify.app/
Status: Test mode (use dummy UPI for Razorpay)
The Real Questions 🤔
- Which features would make you switch from Calendly?
- What's missing from current booking platforms?
- As a developer, what integrations do you wish existed?
- Should I focus on simplicity or feature richness?
- What would make this worth paying for?
My Current Thinking 🧠
- Phase 1 (Launch): Keep it stupidly simple
- Phase 2 (Month 2): Add WhatsApp + better analytics
- Phase 3 (Month 4): API + integrations
- Phase 4 (Month 6): Advanced business features
But honestly, I have no idea if this makes sense! 🤷♂️
What I'm Struggling With 😵💫
- Scope creep: Every day I think of 5 new features
- User research: Limited feedback from real businesses
- Competition: What features do I need to compete?
- Resources: Solo dev with limited time/money
- Technical debt: Some features require major refactoring
The Honest Ask 🙏
I need to ship something in 2 weeks, then iterate. But I want to build the RIGHT next features, not just random stuff.
Your input helps me:
- Avoid building features nobody wants
- Prioritize based on real developer needs
- Focus on differentiation vs competition
- Make smart technical architecture decisions
Quick Vote 🗳️
If you had to pick ONE next feature after launch:
A) WhatsApp integration
B) Google Calendar sync
C) Better analytics dashboard
D) Booking widget for websites
E) Something else (comment below)
Drop your thoughts! What features would make this actually useful for you or your clients?
Top comments (0)