FF Matrix Goes It Alone
Posted by Brandon Kelly on Feb 23, 2010
Ever since I released FieldFrame a year ago, there’s been some confusion surrounding the difference between FieldFrame and FF Matrix. This is entirely my fault, since to date they’ve been bundled together. You’ve never actually downloaded FF Matrix – it just comes with FieldFrame. And many people download FieldFrame for FF Matrix.
Initially the development of the two went hand-in-hand, so it made sense to continue packaging them together, even if it meant dealing with their colliding perceptions. But now that EE2 includes an API that roughly mimics FieldFrame’s, and the two products have begun taking lifecycles of their own, the time has come for them to part ways.
While FieldFrame remains free, FF Matrix now costs $35. That will fund its continued support and development as I work on version 2, which will be a free upgrade when released.
Feed Me
Comments
Michael C.
So, where does that place re-using already-downloaded versions of FF Matrix (as part of FieldFrame)?
Erwin Heiser
Cue much moaning
Seriously, I was kind of expecting this and if it funds continued development then I’m all for it.
Have to agree with Michael C.‘s comment though…
Derek Hogue
Indeed. I just downloaded FieldFrame 1.4. If I upgrade FieldFrame on a site using FF Matrix 1.3.5, should I expect it to continue to work?
The decision makes perfect sense, and I have no problem paying the license fee for new sites, but I think some clarification on the specifics is needed.
Philip Zaengle
Well worth it.
Brandon Kelly
You’re free to continue using FF Matrix 1.1.5 with FieldFrame 1.4 – they’ll work fine together. Just remember to backup ff_matrix along with your other fieldtypes when updating FieldFrame
Derek Hogue
Excellent to hear, thanks Brandon.
The site is quite tasty, congrats on the launch. (FYI, comment preview button and RSS feed are both seemingly broke.)
Michael C.
Who’s this “Brandon Kelly” character answering as if he’s in charge? I don’t see his name in the domain - where’s the answer from Mr. Pixeland Tonic?? :p
Seriously, though, thanks for the clarification, BK.
Shane Robinson
I’m thrilled to pay for FF Matrix and support continued development and support. I have an Internet Radio site that will begin development soon and FF Matrix will be the cornerstone of how the site works.
John Faulds
Looking at the docs for FF Matrix now they don’t seem to be as comprehensive as they were before. I could just be imagining that but I can’t check against the old version because it now redirects here.
Brandon Kelly
FF Matrix never actually had its own docs – just a single page within FieldFrame’s docs.
Paul Burton
**You’re free to continue using FF Matrix 1.1.5 with FieldFrame 1.4 – they’ll work fine together. Just remember to backup ff_matrix along with your other fieldtypes when updating FieldFrame
**
I’ve made heavy heavy use of Fieldframe, FF Matrix, Playa, Ngen, Wygwam along with the basic fieldtypes for use with a number of websites.
Before I jump in and start updating willy nilly, I’d like a little more clarification on your comment noted above.
If I have the last version of FF and FF Matrix installed - 1.3.5.
• When updating to FF 1.4, if I choose not to update to FF Matrix 1.5 — DO Playa, Ngen, Matrix, and Wygwam remain in the Fieldtypes folder?
• When updating to BOTH FF 1.4 and Matrix 1.5 — I am removing Playa, Ngen, and Wygwam from FF 1.3.5 and installing these fieldtypes into Matrix 1.5?
When updating BOTH, what will happen, if anything, to DB content utilizing these fields?
Michael C.
Paul Burton: AFAIK, all the extra fieldtypes are merely additional folders under the FF folder. Updating FF should not affect any files in those additional folders, thus I don’t believe that any updates will remove any existing, 1st/3rd-party fieldtypes.
running with scissors
if the previous version is still free, i’m curious as to what sets ff matrix 1.5 from it’s predecessors so that i can justify paying for it. the new site, which is lovely by the way, does not clearly spell that out unless i missed something.
Brandon Kelly
The previous version simply isn’t available anymore. If you want to use FF Matrix on a new site (or want the features added in 1.5 for an old site), you’ll have to front up for it.
FieldFrame and FF Matrix were released at a time where EE development was just a hobby for me. I had a separate full-time job that paid the bills, and this was just done on the side.
But now that I’ve quit that job and decided to make EE dev a full-time thing, I can’t afford to continue giving big things away for free (especially considering the toll it takes on my time to support).
The reward should be clear, though – you’ve now got 100% of my time devoted to making these things better and helping you with the implementation.
running with scissors
fair enough.
Mitchell Kimbrough
Just giving Brandon a friendly “cheers” for going full time with EE dev work. EE sites are going to get a lot more powerful now through your full time efforts. And you are certainly earning your pay.
mk
Brandon Kelly
Cheers Snoodly!
Chad Crowell
Might I suggest a “Top Shelf” package - maybe a bundle, single site license product that contains playa, matrix and wygwam? I tend to use all three for most sites I build now.
running with scissors
i second that idea.
Brandon Kelly
I’ve considered a bundle, as well as a few different forms of volume discounts. If I go with a bundle, I’ll probably hold off until everything is EE2-compatible.
Hyperatic
+1 on the bundle.
Thanks for your hard work Brandon.
Erwin Heiser
+1 on the volume discounts, per 5 or per 10 licenses would be a good start.
Matt Weinberg
+1 on some kind of bundle from me as well!
David Wall
May I also add my +1 on the bundle!
outline4
+ 1 for the bundle!
and keep in mind that the freelance version is just 99$... ffmatrix is a third of the whole system…
I will need ffmatrix on ALL of my sites, so please make it as cheep as you can, or give bulk options, freelancer licences, or even EE pro licences…
I love all of your add-ons! and I am happy to pay all of them… but… things start to get a ‘little’ pricy per default install!
On a typicall power install I use the following add-ons:
wygwam 35$
ffmatrix 35$
playa 75$
LG better meta 40$
LG Multilanguage 20$
structure 65$
EE pro 299$
primary category 25$
tag 40$
user 100$
forum 100$
MSM 200$
this is just over 1000$
well… for some websites it’s not a big deal but for others… this might be a deal breaker…
and if I imagine paying for all the other free add-ons… I would prob. spend 2000$.
still: you’re my personal hero
Simon
When are you going to release Matrix 2.0?
My use of EE 2.0 for client work depends on this and an ETA would be useful.
Craig Allen
Brandon, besides the bundle concept perhaps you might consider non-profit pricing. I spend a lot of time building sites for community organisations such as conservation groups and want to do more in future. These folks have minimal or zero budget, so the costs will become harder to cover as the various addons go commercial.
homepage
Thanks for writing