Better Workflow - News
EE3 Support : March 16th, 2016
Over the past few weeks we've received lots of emails and tweets about our plans for EE3 support. I want to apologise for the radio silence on this but we needed time to carefully evaluate our position before we made a statement.
As we've said many times before, we created BetterWorkflow because it was the tool we needed to use (and sell) ExpressionEngine. When we made it commercially available we weren't at all sure anyone else would be that interested and were surprised by the response.
For a few years everything was great; we gave it as much love as we could (we're a small team and there are only so many developer hours in the week) and continued development to meet the needs of our clients as well as the add-on users. Looking back, there were times when we were more reactive than proactive but I like to feel we looked after everyone who bought a licence.
But now we are in a brave new world and as a business we need to make a crucial decision; do we build our next green field site using EE3?
We've been ExpressionEngine champions for a long time and having looked over EE3 can see that as a piece of software its in great shape; if it was just a technical decision it would be easy. But there are many factors to consider, and key amongst these is the frustrating fact that for us EE continues to be a hard sell.
Most of Electric Putty's work is the not-for-profit sector and often (perhaps mistakenly) 'open source' is a key requirement. Over the years we have worked hard to promote the benefits of a centrally maintained, commercial system but have not always been successful.
So we find ourselves back where we began, without workflow EE isn't an option so we either invest the time to migrate BWF and continue the up hill struggle to persuade potential clients to use EE, or we use this natural punctuation point and move to another CMS which already has this feature.
Just looking at the numbers we can't justify migrating BWF purely to sell as an add-on, the only way it makes commercial sense is if we use it ourselves.
So, in summary, I'm afraid to say we are not currently working in a EE3 migration for BWF. We will continue to support the EE2 version but not develop new features. This is not to say we are saying good bye to EE forever, but we need to think carefully about which technology to invest in next. If we do decide to adopt EE3 then a new version of BWF will follow, so watch this space for updates.
If you have any questions or comments on this we'd love to hear from you.
Malcolm and the whole EP team