Shopware Plugin Development: Community Feedback on a New WebP Converter and UI/UX Choices
Seeking Testers: A Shopware Developer's Journey with a WebP Converter Plugin
A recent Shopware forum topic, titled 'Ich such freiwillige die meine neuste Plugin idee testen möchten' (I'm looking for volunteers to test my newest plugin idea), sparked an interesting discussion around early-stage plugin development, user interface (UI) choices, and technical implementation within the Shopware ecosystem.
The Plugin Idea: A WebP Converter
The original poster, DannyBO, introduced a new plugin idea: a WebP converter. This tool aims to optimize images by converting them to the WebP format, a crucial feature for improving website performance and loading times. DannyBO openly admitted that the WebP converter component was still in its very early stages ('erste geh versuch' - first attempts) and was seeking volunteers from the community to test it.
Community Feedback on UI/UX and Implementation
The core of the discussion quickly shifted to the plugin's integration into the Shopware admin panel. Max_Shop, a prominent community member, offered constructive criticism regarding the placement of the plugin's settings. He argued that functionalities not used regularly, such as a WebP converter (which could potentially run via a ScheduledTask), should not clutter the main admin menu. Max_Shop suggested that if every plugin developer added direct menu entries for infrequent tasks, the admin interface would quickly become overwhelming and confusing.
DannyBO responded to this feedback, explaining his current approach and his reservations about ScheduledTasks. He mentioned a past negative experience with ScheduledTasks in WordPress, which led him to prefer a more direct menu entry for now. He also clarified that the WebP converter part was not yet fully developed. Screenshots provided by DannyBO showed the plugin's settings accessible under 'Extensions' and 'Content' in the Shopware admin's right-hand menu.
Another technical point raised by DannyBO was the necessity of a config.xml file. He stated that Shopware itself 'meckert' (complains) if this configuration file is missing, which influenced his design choices for handling plugin settings.
The Human Element: Banter and Learning
Beyond the technical discussion, the thread also featured some light-hearted banter. EikeBrandtWarneke playfully pointed out the irony of DannyBO, a 'power user' often critical of other plugin developers' pricing and update speeds, now facing similar challenges and receiving direct feedback on his own developing plugin. This exchange highlighted the realities of plugin development and the often-complex balance between user expectations, technical feasibility, and development costs.
Ultimately, the thread served as a valuable insight into the iterative process of plugin development, the importance of community feedback, and the ongoing debate around best practices for UI/UX and technical implementation within the Shopware admin environment.