Developer Setup and Handover Best Practices for Glide Projects
1. Establishing a Written Agreement
Before any development begins, it’s essential to have a written agreement or contract between the developer and the client. This contract should clearly define:
Scope of work - what the developer is expected to deliver.
Ownership and intellectual property rights - who owns the completed Glide app, data, and assets?
Reuse or resale rights - whether the developer retains permission to reuse the app or parts of it for other clients.
Payment terms and milestones - including deposits, progress payments, and final delivery.
Support period - whether the developer will offer post-delivery support, and for how long.
💡 Tip: Clearly define what constitutes “project completion” (for example, the app is deployed and accepted by the client, or documentation is delivered).
2. Setting Up the Project in Glide
To ensure that ownership and billing remain with the client:
The client (end user) should create their own Glide account and team (workspace).
The developer should be added as a team member with the appropriate role (usually Editor or Admin, depending on the scope).
The client should manage all billing and subscription plans, including any data sources (such as Airtable or Google Sheets) that the app relies on.
The developer should work inside the client’s workspace to build and test the app, ensuring that:
All integrations (APIs, custom code, etc.) are connected under the client’s credentials.
Any external services (e.g., OpenAI keys, Google APIs) are owned and managed by the client.
🔐 Why this matters: This setup guarantees the client has full control over their data, billing, and app access once the project is finished.
3. Development Workflow Best Practices
During the project:
Version control: Use Glide’s app duplication to create checkpoints before major updates.
Communication: Maintain regular progress updates with the client; weekly or milestone-based check-ins work well.
Testing: Involve the client in user acceptance testing (UAT) before final delivery to ensure the app meets their needs.
Documentation: Provide comprehensive documentation that includes the app's structure, data sources, integrations, and clear instructions for future edits.
4. Handover and Project Completion
When the project is complete:
Ownership confirmation: Ensure the app, associated data, and any connected services are fully owned and accessible by the client.
Remove developer access: After final approval, the developer should be removed as a team member (unless ongoing maintenance is agreed upon).
Deliver documentation: Share a short guide that includes:
A summary of app functionality.
Instructions for making simple edits.
Contact info for ongoing support, if offered.
Final invoice and closure: Send the final invoice and confirm project acceptance in writing.
Optional ongoing support: Offer maintenance packages or a retainer for post-launch updates and troubleshooting.
5. Optional: Developer Portfolio and Reuse Rights
If the developer wishes to reuse the app as a template or example:
Obtain written consent from the client.
Remove all client-specific branding and data before reusing.
Clearly state in future contracts whether reuse rights are granted.
6. Ethical and Legal Considerations
Respect client confidentiality and data privacy at all times.
Follow Glide’s Terms of Service and ensure compliance with any connected third-party platforms.
Make sure clients understand that Glide hosts and manages app infrastructure, not the developer.
Summary
Setting up a Glide app through the client’s account ensures transparency, proper ownership, and smooth handover. A structured agreement, clear workflow, and defined end-of-project process protect both the developer and the client, leading to a more professional and trustworthy experience.