I am Dev Nader, and I am writing to propose a user experience (UX) enhancement for the extension search interface within the GDevelop editor.
The Current Problem: In my usage (and I believe many other users share this view), the process of repeatedly searching for the same extensions in new projects is quite time-consuming and tedious. Furthermore, the current “list view” in the extension search window can be visually cluttered, which, combined with the small font size, makes quick browsing less efficient.
The Proposed Solution: I have developed a rough prototype showcasing two key features implemented here as an AI-assisted proof-of-concept to demonstrate the value:
Favorites System: Add a “star” icon to each extension, allowing users to save their frequently used extensions to a dedicated tab. This would grant instant access to common extensions in any new project, completely eliminating redundant search effort.
Grid View Mode: Implement a toggle to switch between the current list view and a new grid view. A grid view, featuring larger icons and a cleaner layout, would be visually much clearer and far better suited for rapid, efficient browsing.
Context: These features were implemented and tested in an experimental prototype. My goal in sharing this is to present a concrete concept to the development team. I hope you will evaluate the potential of this implementation for a polished, official inclusion in a future update to enhance the workflow of all GDevelop users.
I have attached a images and video demonstrating the prototype in action. I look forward to hearing your thoughts and the community’s support!
i like the way you think, and i totally agree with all of it. the only thing im worried about is that your prototypes are maybe too nice for gdevelop’s design language. gdevelop’s design language is not pretty.
I know that some aspects of the engine aren’t very nice in terms of design… but for your information, everything I showed in the pictures works for me in my personal custom version of the engine.
I already have a forked version of it, but I haven’t published it yet—it’s for personal use. If you want, contact me on Discord (my account is nb24) and I’ll give you a link to download and try it. It includes several changes and improvements I made to enhance certain features and the way it works to suit my usage. I think many people will like it.
However, I hope that anything I release here publicly will be seen by others and get support so that it can be added to the official engine version
I have one question to better understand your interaction with the tool: do you use the search bar in the Extension list? No → why, Yes → where do you think it’s not fulfilling your need of search?
Yes, I do use the search bar in the Extension list.
However, I’ve noticed a few challenges that make discovering and adding extensions less efficient and sometimes more time-consuming:
Speed of access: When I want to quickly find and add extensions I use or need frequently in my projects, I often have to repeatedly type their names or scroll through the list. A favorites system could reduce this repetitive searching and save time.
Remembering names: If I forget the name of an extension, it slows down my workflow because I need to search or browse multiple times to locate it.
Having a way to mark extensions as favorites would make finding and adding the extensions I use or need frequently in my projects much faster, improving workflow efficiency and saving time.
Thank you for taking the time to consider this suggestion!
I’d like to pose a counter-question for consideration :
Why do social media platforms and online stores and other website implement a favorites or bookmarking system even though they already have a search bar? It’s worth reflecting on this—favorites help users quickly access, save, and organize items they use frequently or want to revisit, which search alone can’t fully provide.
This perspective might help inform how a favorites system could enhance the Extension list experience as well.
Hello DevNader,
Thank you for your answer.
That is what I thought was happening, but I wanted to confirm (because some other times people have given me other reasons).
As for your counter question: each online platform has its own reasons for UI patterns and functionalities so I wouldn’t generalise, but even tho searching is faster, it relies on memory (the words used to find the element should match in order to find what the user tries to find). Indeed, “recognising what you’re looking for from a shorter list rather that having to search for it in a long list” is a better option for certain cases and screens.
I have my reservations on the disposal of the elements (I think a list requires less eye effort to visually scan than a grid), but l’ll let the community upvote the need for “keeping the most used extensions at the top for easier access”.
: