How this works
PluginGap does not predict startup success. It tries to reduce bad ideas by combining a few kinds of evidence, developer demand, what already exists, and whether Roblox actually lets you build the thing.
We start with things developers have publicly asked for. Then we group similar requests, look for plugins that already solve them, check what Roblox Studio actually allows plugins to do, and remove ideas that do not hold up.
About the score
The score reflects how well an idea matched the research criteria — developer demand, existing competition and technical feasibility. It is not a prediction of product success, demand or revenue.
The steps
1. Find requests
We collect feature requests and recurring problems developers talk about, right now from the DevForum.
2. Group similar problems
Requests that seem to describe the same underlying problem are put together, so one workflow pain is not counted as ten different ideas.
3. Check existing plugins
We search the Creator Store for things that already solve it.
4. Check Studio
We look at Roblox's APIs to see whether a plugin could realistically do the job.
5. Keep or reject it
Ideas that seem crowded, impossible, too small, or already solved get filtered out here.
6. Look again
For the ideas that survive, we search specifically for competitors before treating them seriously.
Where this can be wrong
Statuses reflect the current evidence. Findings can change when Roblox changes Studio or its APIs, adds native features, or new Creator Store plugins appear. When an idea is rechecked, its last checked date can be shown on the idea page.
- This is research, not a prediction.
- We can miss plugins. Our searches are not guaranteed to cover every plugin on the Creator Store.
- A request does not mean someone will pay for a plugin that solves it.
- Roblox can change its APIs at any time.
- An idea appearing here does not mean it will become a successful product.