Glide Specialist – Frontend Mini-App (Client & Staff)
Budget: $15 – $25 USD
We are building a production-ready MVP for a barbershop, focused on real-world salon operations, not a prototype.
We are looking for a Glide specialist to own the frontend layer of the project (Client App + Staff App), working in parallel with a dedicated backend/integrations developer.
This role is strictly frontend / no-code.
All business logic lives in the backend.
⸻
Project Context
• Frontend: Glide (Web App)
• Client App
• Staff App
• Backend: handled by a separate developer (Make / n8n / custom backend)
• Database: PostgreSQL (Supabase)
• POS & Payments: Shore + Stripe (backend-driven)
This is NOT:
• a PWA project
• a custom React/Vue app
• a backend role
⸻
Your Responsibilities
• Build the Glide Client App:
• onboarding (OTP-based)
• check-in flow
• service & barber selection
• queue status display
• Build the Glide Staff App:
• staff check-in
• queue management
• service execution
• extras selection
• Configure Glide data relationships correctly
• Use computed columns and visibility rules properly
• Connect Glide to backend endpoints (actions, webhooks triggers)
• Ensure clean UX and fast flows (≤60s check-in)
Required Skills
• Proven experience with Glide (advanced level)
• relations
• computed columns
• conditional visibility
• actions & workflows
• Ability to structure Glide apps cleanly (maintainable, scalable)
• Understanding of frontend ↔ backend boundaries
• Experience working with external APIs / webhooks (via Glide actions)
• Strong UX sense for operational apps (staff usage)
⸻
Nice to Have
• Experience with Supabase as a Glide backend
• Experience on multi-role apps (client vs staff)
• Familiarity with POS-style workflows (queues, tickets)
• Experience building apps used in physical locations
⸻
What You Will NOT Do
• Backend logic
• Pricing calculations
• Payment handling
• Subscription validation
• Database business rules
⸻
Project Setup (Important)
• The Glide project will be owned by the client
• You will be added as Editor / Developer, not Owner
• Clear specifications (functional + technical) are provided
• No scope creep — MVP is strictly defined
⸻
To Apply
Please include:
• Examples of real Glide apps you built (not tutorials)
• A short explanation of how you structure Glide apps
• Confirmation that you understand:
• Glide is frontend only
• Backend is the source of truth
We value clarity, discipline, and real-world usability over fancy features.
If you are a true Glide specialist, this project will be a great fit.
We are looking for a Glide specialist to own the frontend layer of the project (Client App + Staff App), working in parallel with a dedicated backend/integrations developer.
This role is strictly frontend / no-code.
All business logic lives in the backend.
⸻
Project Context
• Frontend: Glide (Web App)
• Client App
• Staff App
• Backend: handled by a separate developer (Make / n8n / custom backend)
• Database: PostgreSQL (Supabase)
• POS & Payments: Shore + Stripe (backend-driven)
This is NOT:
• a PWA project
• a custom React/Vue app
• a backend role
⸻
Your Responsibilities
• Build the Glide Client App:
• onboarding (OTP-based)
• check-in flow
• service & barber selection
• queue status display
• Build the Glide Staff App:
• staff check-in
• queue management
• service execution
• extras selection
• Configure Glide data relationships correctly
• Use computed columns and visibility rules properly
• Connect Glide to backend endpoints (actions, webhooks triggers)
• Ensure clean UX and fast flows (≤60s check-in)
Required Skills
• Proven experience with Glide (advanced level)
• relations
• computed columns
• conditional visibility
• actions & workflows
• Ability to structure Glide apps cleanly (maintainable, scalable)
• Understanding of frontend ↔ backend boundaries
• Experience working with external APIs / webhooks (via Glide actions)
• Strong UX sense for operational apps (staff usage)
⸻
Nice to Have
• Experience with Supabase as a Glide backend
• Experience on multi-role apps (client vs staff)
• Familiarity with POS-style workflows (queues, tickets)
• Experience building apps used in physical locations
⸻
What You Will NOT Do
• Backend logic
• Pricing calculations
• Payment handling
• Subscription validation
• Database business rules
⸻
Project Setup (Important)
• The Glide project will be owned by the client
• You will be added as Editor / Developer, not Owner
• Clear specifications (functional + technical) are provided
• No scope creep — MVP is strictly defined
⸻
To Apply
Please include:
• Examples of real Glide apps you built (not tutorials)
• A short explanation of how you structure Glide apps
• Confirmation that you understand:
• Glide is frontend only
• Backend is the source of truth
We value clarity, discipline, and real-world usability over fancy features.
If you are a true Glide specialist, this project will be a great fit.