I’ve ended reading over the article (and the comments) a number of times because I think there are some really, really great though as it relates to using WordPress as an application platform.
This is something that I’ve talked about a number of times and it’s something that I really want to see happen more and more in the future; however, this is one of the first times that I’ve really seen someone take WordPress, use it as a foundation for solution that’s built towards a specific market, and then articulated it in such a way that does a great job of expressing what exactly it means for WordPress to be an application platform.
Pickle and WordPress: An Invisible CMS?
When I first read this in the title of the article, I was immediately intrigued and actually a little skeptical as to what I was about to read. Most of the time, you know, we’re all proud to wave the WordPress banner and the idea of burying WordPress seemed to be in strong opposition to that.
But reading a little bit further (which is always a good exercise as it relates to any form of news :) showed this (sourced from the original article):
“That data (in my opinion) is exclusive to what I’m doing with Pickle,” he said. “In other words, I’m not concerned with my users even knowing that it’s powered by WordPress.”
That is part of what it means to be using WordPress as an application foundation. Sometimes I think that we get so caught up in the bubble of our peers, our own projects, and our peers’ projects, that we forget to think in terms of the market who would use such a solution.
Permitting it solves a problem, what does it matter what it’s powered on? Don’t take this idea too far – I mean I’m not advocating for building solutions on sloppy foundations – but when you find an app for, say, your phone do you care that it’s written in Objective-C or Swift?
Sure, some purists might, but the general, non-technical end user who needs a problem solved? Nope.
They want something that looks good, functions well, meets a business need, and allows them to focus on their business and/or their core competency. In the case of Pickle, it’s preparing and service food. It’s not about arguing over how the site is getting to the browser.
Pickle and Best Practices
If you’re a WordPress developer, this is where the alarms start going off and you immediately want to dismiss the solution as a piece of junk.
“You mean it doesn’t follow our conventions or our style guide? Out with it!”
And I’m certainly not saying that we should go this way, but I do think that there’s a time and a place for us to honor all of the coding standards that we have (especially in themes, plugins, and other publicly released work), and then maybe relax when we’re talking more about something that’s not going to be used as widely by developers, designers, and so on.
Again, this is essentially a SaaS (well, unless you download it, but I digress on that point). Does it work? Does it work well? Does it solve a business need?
Oh, so Yoda Conditions aren’t used throughout the codebase. I guess it’s not a worthwhile solution.
I applaud Jason for taking a step outside of the usual bubble (to be clear, a bubble that I think WordPress developers shouldn’t try to pop, but to expand) to meet a business’ needs.
Pickle in the Future
All minuté details aside, I highly recommend reading the original article and checking out Pickle. It really, really does a great job of showcasing what we’re capable of doing with WordPress as a web application platform, how we can expand beyond what we’re used to seeing, and how we’re going to be able to go even further when the REST API is eventually released.
Props to Jason, what he’s doing, and Tavern’s coverage. I can’t wait to see more things come out like this.