Spreadsheets suffered a body blow when Salesforce announced new platform functionality last week. Soon all spreadsheets will be good for is financial analysis. This sounds funny because the spreadsheet has for several decades been the unofficial IT prototyping tool. Actually, it was the end user prototyping tool, the default thing they used to capture data when IT was famously too busy maintaining the legacy systems they got from a spaghetti factory. But with the introduction of Lightning Components, Lightning App Builder, and AppExchange for Components, it’s now easier to build your prototype app with these tools than it is to build a spreadsheet.
Salesforce glommed onto lightning terminology as a way to convey the idea of fast development and because it sounds so much better than blitz. The idea in total reminds me of object oriented programming from 30 years ago but with much less emphasis on tedious coding and libraries. Salesforce has brought to market tools that can take a back seat to your creativity and rather than obsessing about how to do some technical trick, the developer, or increasingly the end user, can think about the business need. It’s as fundamental as an artist mixing a color without giving it a lot of conscious thought. That’s what’s happening here with components. Let us unpack.
Ok, so the really cool thing to me is that components will become another category in the AppExchange. They can be built by anyone and if they can be built they can be bought and sold. Of course you can spend a week building one yourself but having the functionality available on the AppExchange for pennies (ok, whole dollars) will make everyone think twice when making build vs. buy decisions.
Components come together in the Lightning App Builder a place (I believe they refer to it as a canvas in keeping with my art analogy) where a developer goes to assemble (I think they say compose) the business app. I suppose you could think of the canvas as a blank spreadsheet if that helps.
But the difference between a spreadsheet and a functioning app is huge. It goes without saying that unlike a spreadsheet, a Lightning app has a real database behind it. And as usual with Salesforce, apps built on the platform inherit all of the other Salesforce capabilities like workflow, Chatter, and security schema and everything else.
A few years ago you could look at the mountain of legacy code and wonder how it could ever be rewritten for handheld devices or replaced to take advantage of all the new capabilities coming on stream. Those capabilities are substantial because, more than the transaction-oriented applications that are rapidly being replaced, they focus on various aspects of process.
Thus the answer to the how question above has two parts. First, we aren’t going to replace those transaction systems, we will supersede them with process support that goes wider and deeper, made possible by pre-built components and subsystems. Second, we will do this because the market demands it. No one is waving a flag to that effect but I don’t think you can be in business in a social, mobile, big data world any more and not know that if you can’t leverage those things you will need to find a new job.
Finally, and also in answer to the how question above, all of this is now possible because we have the ability to generate apps replacing man-centuries of work in hand coding. With this as the fuel of business innovation, I am excited to contemplate where it takes us.
(Cross-posted @ Beagle Research Group)