• Great plugin and excellent customer support. I’ve used other simple-to-use donations plugins that turned out to be too simple but Give hits the sweet spot of needed features without being too complicated. As an aside to the developers, I am concerned that in its ongoing evolution it’s getting too feature-rich (i.e., code bloat) and suggest more things get put into the add-ons which can be installed or not as needed. Determining what is core and what is add-on can be a fine balancing act, but shouldn’t be ignored or an after thought.

    • This topic was modified 4 years, 6 months ago by jimmathis.
Viewing 1 replies (of 1 total)
  • Plugin Author Matt Cromwell

    (@webdevmattcrom)

    HI @jimmathis Thank you so much for your very kind review — the success you’re experiencing is EXACTLY why we built GiveWP.

    I’d love to hear more details about which features in GiveWP core are specifically unneeded or unwanted. The balance between whether it’s in Core or an add-on is a conversation we have continually — it’s been central to all our decision-making and NEVER an after-thought. We do generally want to make sure that the features that are in Core are what at least 80% of our free users actually need and want.

    From my perspective as well, “code-bloat” is not the same as “feature rich”. Those are two different concepts. Bloat is code that sits unused and unneeded, whereas having a lot of features are a reflection of wanting to address the needs of our users.

    Anyway, would love to hear more on your perspective there, specifically what — if any — current features are unneeded or unwanted.

    Thank you!

Viewing 1 replies (of 1 total)
  • The topic ‘Much better than the competition’ is closed to new replies.