Template Store Guidelines

How to create Glide templates that people will love

If you've got a great app you'd like to submit to the template store, we would be happy to review it. Help us speed the process up by following these guidelines. Templates that do not meet these guidelines will not be approved, and will be returned to you to revise and resubmit.

Here’s a simple look at what your template should and should not do.

Templates should:

• Have privacy setting set as “Users in the users table”.
• Have user profiles setup.
• Be built in English.
• Be visually appealing.
• Be self-sufficient, stand-alone apps.
• Be predominantly designed for internal business use.
• Use neatly organized Glide Tables (i.e. clear formatting, functions/formulas computed in Glide's data editor, grouped columns, etc.)
• Avoid private or personally identifiable data and images (use fake names, stock photos, etc.)
• Solve for a specific use case, and be really good at one thing (not mediocre at multiple things.)
• Have a clear, complete description. Write a comprehensive description that includes the problem your template solves, its features, and its benefits to the end user. This will help more people discover your template via search engines.
• Optional: Include a video that demonstrates the template’s features and explains its purpose. If you do include a video, it must include a voiceover with of someone explaining the template—merely showing your template and wiggling your cursor over it is not enough.

Templates should not:

• Contain private or personally identifiable information. For example, an Employee Directory template must not contain the real information of actual employees or people—it should contain 'dummy' data only.
• Contain offensive, profane, obscene, libelous, or otherwise illegal content.
• Contain any malicious or deceptive content.
• Contain visibility conditions: To make it easier for users to discover the features and components of your template, we suggest you avoid using conditional visibility, particularly on entire screens.
• No clones of social networking or dating apps like Tinder, Facebook, or messaging apps.
• Templates must not be merely lists or indexes of content. For example, a template that consists of a list of jokes will not be approved.
• Rely on configuring third-party services or other additional functionality, whether free or paid, outside of Glide (for now, this means Zapier integrations, too). In other words, your app should work immediately after someone copies it, with no additional setup required outside of Glide.
• Use HTML/CSS embedded within Rich Text components to inject styles or special functionality not normally supported by Glide into the app.
• Contain advanced actions (multi-step actions) or integrations. Currently Templates do not support integrations. We will be launching integration functionality for our templates sometime in the future, and will keep you posted.