David, Mitja and Igor work on a great product called FrodX. Their idea was to create modules for popular eCommerce platforms and support major versions, for example Magento 1 and Magento 2. Optiweb helped them creating document how modules should be working, on which event it should hook up and so on. Frodx went on looking for a partner who would develop a set of modules for them, for example like Braintree hired Gene agency.
Optiweb said we are a good match as we are currently developing WooCommerce modules on WooNinja.si and I have personal experience with developing modules for Magento, Prestashop, Opencart, WooCommerce, ActiveCollab over SpletniSistemi.si and I know all the pains creating a modules for different platforms and versions.
Instead of offering FrodX a development team I have offered them an hour of Business consulting with a promise this will open their mind and think differently. FrodX accepted the proposition and we went back to the drawing table. What we found out is that FrodX would get loads of problems when creating modules for each platform. Why?
- every platform has different major versions and not all customers are on latest one (supporting minor, major versions – different modules for each version)
- every customer can have hard-coded hacks which sometimes disable a specific hook (after purchase hook) and that needs a lot of dedicated time for installing the plugin for the customer, debugging what is wrong
- every customer can have custom template that would not include for example FrodX thank you – confirmation order template part and we would need to add that manually
- supporting all the popular platforms which are constantly updating would mean a lot of work
- developing a module is just a start – the biggest part of work begins when module is done and you need to support the clients
Instead of doing all the pains, we went back to API solution, like MetaKocka has done it.