I used to use it extensively in all of my apps, mostly for the pagination and the holding of lists. I never could fully wrap my head around all of it’s potential as I couldn’t understand the javascript functions built into it. But, Keith helped me with some critical functionality I would have never been able to achieve on my own, and I always recommended the plugin.
I am now. Mostly because some of the plugins that I used so extensively are no longer available, so I needed some ways to replace their functionality. I’ve also wanted to fix some issues, and overall improve the way I build. I’ve been building out my Data Jedi plugin and using it in all of my apps now. In doing that, I think it would help people who use it feel at ease around whether or not it will be maintained and bug fixes pushed, but also that new features will be added and nice little updates for big improvements will find their way into the plugin over time.
One example of that is I just updated the plugin as I’m building in a client functionality to switch all checkbox fields to yes/no fields to allow for more dynamic possibilities. Specifically it allows me to use one plugin element instead of two, or needing to have a conditional on the element and can instead just tie in a dynamic expression with ‘in-line’ conditionals to evaluate to yes/no.
I’m not sure how larger agencies that develop plugins handle things like that, or how many plugin developers are using everything they build in their own apps, but I think overall, most plugin developers I’ve seen as active are pretty easy to reach and seem eager to support their plugins.