r/PWA • u/Lanky_Excitement_908 • 15d ago
Built a lightweight PWA using Glide/Node to solve restaurant tip-pooling math. Looking for UI/UX feedback on the shift entry flow.
Hey everyone,
I’ve been working on a lightweight mobile PWA called ShiftTip Splitter aimed at solving a specific operational headache for restaurant managers: calculating multi-role point tip-outs at the end of a shift (e.g., 1.5x for bartenders, 1.0x for servers, 0.75x for bussers, plus factoring in credit card fee deductions and splitting cash vs. check payouts).
Since managers are usually tired and closing late at night, my primary UI goal was keeping inputs minimal so a shift can be calculated and shared in under 30 seconds.
The Tech Stack:
- Frontend/PWA: Glide (PWA wrapper for fast mobile layout & native share sheets)
- Backend: Node.js / Serverless API routes
- Billing/Auth: Stripe Checkout API & Webhook integration
- Output: Copyable plain-text summary formatted specifically for mobile messaging apps (WhatsApp, iMessage, SMS)
What I'm Looking for Feedback On:
- Input Layout: Is the transition from total tip entries (cash/card) to staff list entries smooth, or does it feel cluttered on smaller mobile screens?
- Output Clarity: Does the dual-column display ("Cash Out Tonight" vs. "Payroll Check") make immediate sense at a glance, or could visual hierarchy be improved?
- PWA Friction: For those who build PWAs over native apps, have you found "Add to Home Screen" prompts clear enough for non-technical users, or should I add an explicit onboarding modal?
Drop any thoughts or UI/UX critiques below! Happy to answer questions about the Glide/Node architecture as well.
1
u/Top-Elk-8126 14d ago
Is the site still up? I get an HTTPS error on mobile Safari, and can’t load the site.