Is module development for older versions even relevant anymore?

[innovacy]

I was wondering, if someone was to create a new module for release today, how important would it be still today, to make the module compatible with older PrestaShop versions, specifically either v1.6 or if staying within the 1.7 branch only, for earlier versions than the last 2-3 1.7 releases?

Are shop owners still looking for modules for older versions quite frequently?

I would like to use the advanced features which are available only after versions like 1.7.6, being able to add Symfony services, routes etc. as also using only the newer translation service and even some of the much newer features. If 1.6 should be supported though, many of these just can't be used or can't be used to their full extent. However, I'm hesitant to abandon support for more legacy versions, knowing that if I decide to go that route, there's not one simple way or feasible to make these later compatible with older versions or to turn back.

I don't want to use these newer features just for the sake of using the latest technology, but rather focus on what the actual demand is. However, I don't have enough insight on numbers big enough or something like that myself, to make good conclusions on that.

Would I do best, to skip using those newer and great features and keep the modules more compatible, or rather focus on providing the best value for the latest versions by leveraging these features?

 

 

Edited March 14, 2023 by innovacy (see edit history)