Congratulations to the team + constructive criticism - UI/UX improvements for some Fluent products
I love all of WPManageNinja's products (the ones I use and even the ones I haven't used yet) 🤠 the quality is evident.
But I feel that some of their specialized products (Fluent Auth, FluentSMTP, and FluentSnippets) also need a little more care and attention in terms of modernization 😪. They play a very important role for many, but in this era, where everyone (including the Ninja team) is making improvements to the user experience and visual appeal, these plugins feel somewhat neglected in terms of UI/UX.
For example, another important plugin, like Fluent Forms, has excellent features and has received some visual improvements, but it still needs to feel more modern (backend/frontend) when compared to its other "new" competitor, SureForms, since it's clear that they has a more up-to-date UI/UX (functional differences aside). Also, SureForms components (radio buttons, dropdowns, checkboxes, and others) already have a great predefined style, meaning that forms typically don't require much visual adjustment from the user right from the start (beyond colors, border radius, or spacing) because they have a very pleasing default style. ⚡ That could speed up the form style editing process for average users.
🎉 I'm very excited about the two upcoming major updates for FluentCommunity and FluentCRM. I know nothing is perfect, but you've truly done an amazing job over time.
Thank you for all your hard work, and we really appreciate how you listen to your community 💪.
I would love to see a version like FluentAuth Pro to handle working with different identity providers, like Firebase. There isn't a way to change the 'lost password' link to go to Firebase, so I have to jury rig things and that deletes the beautiful interface created with FluentCommunity/FluentAuth.
It would be nice to have integration to Firebase or other IDPs inside of FluentAuth to avoid relying on 3rd party plugins.
With FluentSnippets, it would be nice to change an existing snippet from PHP to JS, for example, rather than creating a new snippet. Yes, the code has to be changed, but sometimes you figure that you have to pivot in your approach and plop in new code. It's not a major issue, but it would be a convenience.
Thanks for sharing your thoughts, Erick...:)