The summary should answer the question "What superpower does this app give me?". It doesn't need to comprehensively describe everything the app does, as long as it highlights one important aspect and makes it clear why it's valuable.
- Keep it short (35 characters or less)
- Pique people's curiosity
- Use imperative if possible (e.g. "Browse the web" instead of "A web browser")
- Use sentence case
- Technical details (e.g. the toolkit or programming language)
- Structures like "GUI for X" or "Client for Y"
- Mentioning the target environment (e.g. "X for GNOME")
- Repeating the app's name
- Overly generic adjectives like "simple", "easy", "modern", "powerful", etc.
- Articles (e.g. "A ..." or "An ...")
- Punctuation (e.g. a period at the end)
- Title case (e.g. "Chat With Your Team")
- Maps: "Find places around the world"
- Shortwave: "Listen to internet radio"
- Slack: "Chat with your team"
- Tau: "GTK frontend for the xi text editor"
- Contacts: "A contacts manager for GNOME"
- Devhelp: "A developer tool for browsing and searching API documentation"
- Provide multiple screenshots showing off the main areas of the app
- Show off the app with realistic and good-looking example content
- Update screenshots when the app UI changes
- Use GNOME system defaults (stylesheet, font, icons, window decorations, etc.)
- Using a non-standard system stylesheet or icons
- Using non-standard window decorations (e.g. minimize/maximize enabled)
The Gitlab repository icon should be the regular app icon with a baked-in shadow. We have plans to add a way to automatically export a PNG with a baked-in shadow from App Icon Preview for this purpose.