Writing a good feature request

[Sandroid]

Before starting here, please read: How Feature Requests work

This is how you draft a good request.

• One feature at a time. Don’t mix multiple features.
• You can submit as many requests as you want.
• Aim for a self-explanatory title.
• Follow the template provided.
• Use plain English and be concise.
• You are drafting a community feature request, not a personal wish. Refer to the user and not to yourself. Use neutral descriptions, not rants.
• Focus on what you’re feature should achieve, not on how to implement it.
• If available, it’s always useful to add screenshots, diagrams, links to documentation or videos (including those of other products) to illustrate your feature.
• Add two tags, one for the product and one for the main feature.

Note: Feature Requests are editable by others, it’s a living document, wiki-style. All improvements are welcome.

Review and publication on the Feature Request

• All requests are immediately votable.
• Moderators and administrators will review requests, with the goal to avoid incomplete proposals, duplicates, typos, broken links.
• They also check that the community guidelines are followed.

Here’s a detailed look at the lifecycle of a request:

How do feature requests work + some helpful links (Top / New Feature Requests)

As once in a while these questions pop up, i figured let's do a Feature Request Q&A with some additional helpful information. Feel free to ask a question if something is unclear or there is no answer to your question.   Creating a feature request Users can create a feature request in Feature Requests Once a request is created it becomes immediately votable The Moderator Team will review and correct them if necessary. They may also ask some further questions to help clarify the intent of the…