Did you hear the big news?
That ExpressionEngine 3.0 is here? I did, and I'm excited. From what I've read, EE3 will be a good foundation on which to build the future of the ExpressionEngine community. Congratulations to EllisLab.
Is Blocks compatible with EE3?
Boo! Well, do you plan on making Blocks compatible with EE3?
Absolutely. When I started working on Blocks, I believed that it would fill an important hole in the ExpressionEngine community. When I talk to my customers and potential customers, it's apparent that it is playing an important part. The release of ExpressionEngine 3 hasn't changed that: Blocks still has an important part to play in the community.
So yes, Blocks will be compatible with EE3 in the future.
And I would love to give it to you now.
However, I am one person, and I have many responsibilities. I have a wife and children. I have a full-time job. I have a large freelance project with a deadline. I currently don't have a lot of time to work on new Blocks features, including making Blocks EE3-compatible.
Should I feel sorry for you? I don't.
You should not. I only bring it up to address a few points.
Blocks development is not a full-time gig.
There are people behind the software you use. Sometimes it is easy to forget that those people are doing their best to balance the many responsibilities in their lives, just like you do.
The large freelance project that I mentioned? It has a deadline. Which means that it will end.
When it's over, I will have a lot more time to focus on Blocks. And I will. The number one priority will be EE3-compatibility. But there are also a host of features that would make Blocks an even better solution for rich content.
Wait, so are you too busy to provide support for your current customers?
Woah now, hold your horses. For the past couple of months, I haven't been prioritizing new features for Blocks. Support for current customers will always be a priority.
I like to think that I have still been providing a high level of support for my customers. A few have even told me that recently.
When I started Blocks, I didn't know what to expect for customer support, and I set a personal goal to be responsive within a week. Turns out, I've been pretty good at helping out Blocks users within about 1 or 2 days. And while the level of feature development has dropped in the last couple of months, the level of support has not.
OK, OK, so you do plan on working on EE3 compatibility. Can you give me an idea when?
I can't tell you exactly.
But I can tell you this: I will likely start focusing on Blocks again later this year (2015). At that point, I'll have a better idea of how much work it will take to update Blocks, so I'll have a better idea of when it will be ready.
What about upgrade pricing?
Because I sell through Devot:ee, I have two options.
I could release it as a new add-on, which would require a full license fee to use it on EE3.
I could provide it as an update to the current Blocks, which means it would be a free upgrade to all current customers. Blocks does use timed downloads, so customers who purchased Blocks over a year ago will have to pay a renewal price whether they're updating to the EE3 version or to any newer version.
I'll decide which option I use based on how much work is required.
What are your plans for EE2?
Blocks works great as-is on EE2, and will continue to work great, as-is, on EE2. All new feature development will go into the new EE3 version of the add-on.
I think this is fair. The community will likely treat EE2 as a legacy platform going forward. And being able to focus on a single platform means that features can be delivered faster than if they need to be developed for multiple platforms.
What if I have more questions?