I need your brutally honest feedback on GMB Booking - my booking platform that's currently in test mode. I've been heads down coding for weeks, and now I need fresh eyes to tell me what's working and what's complete garbage.
What I'm Looking For 🔍
Real user experience feedback:
- Is the booking flow intuitive or confusing?
- Does it feel fast or sluggish?
- Any UI/UX decisions that make you cringe?
- Where did you get stuck or frustrated?
- Mobile experience - smooth or janky?
Test It Out 🚀
Platform: https://gmbbooking.netlify.app/
How to test:
- Try creating a booking as a customer
- Go through the complete flow (including payment)
- Test on both desktop and mobile
- Payment: Use dummy UPI details (Razorpay test mode)
Specific Questions 🤔
- First impression: What's your immediate reaction? -** Booking process**: Too many steps or too simple?
- Payment flow: Feels secure or sketchy?
- Overall experience: Would you actually use this?
- Compared to others: How does it stack against Calendly/Fresha?
What I'm Worried About 😰
- Is the onboarding clear enough?
- Does the booking confirmation feel trustworthy?
- Are there any obvious bugs I'm blind to?
- Is the value proposition clear from the UI?
Current Status 📊
- Development: ~95% complete
- Testing phase: Looking for breaking points
- Performance: Decent but could be faster
- Mobile: Works but needs polish
The Real Talk 💯
I've been staring at this code for so long, I can't tell if it's actually good or if I'm just used to it. I need developers who will:
- Actually click around and test stuff
- Point out stupid design decisions
- Tell me if the flow makes sense
- Find the bugs before real users do
Quick Feedback Format 📝
If you test it, just drop a comment like:
- Overall: Good/Bad/Meh
- Flow: Smooth/Confusing/Broken
- Speed: Fast/Slow/Acceptable
- Mobile: Works/Doesn't work/Needs work
- One thing to fix: [Your biggest complaint]
What's Next 🎯
Planning to launch in 2 weeks, so this is my last chance to fix major UX issues before real users start complaining.
Your feedback directly impacts the final product! Don't hold back - roast it if it deserves it. 🔥
Top comments (0)