When opposites don’t attract: The app vs The platform

NoCoding

The IT world is a dichotomy.

On one hand we have our peers and educators telling us that to learn to code creates a foundation for entry into the world of the software business and yet in our own enterprise domain we yearn for the ability to create without code. Take a look at the startup scene and once again we find examples of lean and agile apps which allows a user to quickly imagine and prototype what the experience and process will look like.

No code prototyping

AppGyver is one such example, it’s a mobile app prototyper, aimed at those who need to rapidly iterate on designs during the mobile app-dev process. While is doesn’t mean that the prototype is anywhere near a finished product the fact you can build the look and feel in minutes is a standout feature.

I look at the enterprise platform industry and it’s as far removed from the above example as possible. I’ve seen plenty of marketing from vendors about their ‘no coding’ approach to building process based applications but it always falls way short of the promise. When an organisation invests in a platform it expects to be able to rapidly prototype and show its business users just what it will look and feel like without the need for significant investment in technical upskilling of its business workforce.

But the problem is two-fold;

  • the platforms themselves are not as agile as they make out. They require analysis, requirements gathering, technical input, data, connectors, training, in order to make something look remotely feasible and workable.
  • the methods we apply in business transformation are too deeply rooted in the past to allow lean startup approaches. You only have to look at PMP and Prince2 to recognise there’s nothing in there that means agile. Even SCRUM doesn’t lend itself to prototyping this way, in reality it still takes days/ weeks not minutes/ hours.

Opposites don’t attract

The IT world is indeed a dichotomy.

Modern enterprises are looking to move swiftly toward a leaner, app-centric approach. One which allows the business user more input into design, process and implementation without the need for technical expertise in the earlier stages. But enterprise platform vendors are a long way off in understanding this trend and still deliver solutions which are the exact opposite.

And in this case, opposites no longer attract and those platforms will be pushed out in favour of the app.

Tags: , , , , , , , ,

No Responses to “When opposites don’t attract: The app vs The platform”

  1. March 2, 2013 at 1:12 pm #

    @ Theo Priestley - I agree with you that IT world is dichotomy. IT world can be divided into two parts - business technical and Coding technical. IT world believes that creating business software is an art. But my understanding is that it is not a art but a science.

    Creating business software similar to the business application requires knowledge of across industries, across functions, across business processes and knowledge of behavior science and It interfaces. IT world believes that it is not possible to learn all the knowledge by one person. That is why SAP produces specialists of one module NOT the SAP specialists.

    If you find any sponsor interested to code the body of knowledge and create business software, which can convert your thoughts to reality, please let me know

Leave a Reply