The New Productivity Platforms: Your Solution To The AD&D Crunch

For fast delivery of new business applications, conventional Java and .NET coding is usually no longer your best choice. Instead, a generation of new productivity platforms holds the potential to speed initial application delivery and ongoing updates. These platforms abstract away configuration chores, repetitive coding tasks, and long testing and quality assurance (QA) cycles. Some allow application development and delivery (AD&D) teams to delegate application delivery — in part or in whole — to business experts. AD&D teams under pressure to deliver more with less should evaluate these platforms. This research outlines this emerging category's benefits and risks. Full report URL: http://www.forrester.com/rb/Research/new_productivity_platforms_solution_to_ad%26d_crunch/q/id/58576/t/2. (Note: Pay wall.)

Most application development and delivery teams have simple marching orders: "Do more with less — and fast. And when you've done more with less, figure out how to do even more with still less on your next set of projects. And deliver even faster."

We've not met a single application development and delivery professional during the past two years who isn't struggling to meet this imperative. Why? Competitive markets, business models, and consumer preferences change so quickly, and keeping up requires either making changes to existing software or writing entirely new applications.

Clients react to the AD&D crunch in a variety of ways, but one of the most common responses is to search for new development processes and tools. And right now, AD&D teams will find that a bumper crop of new development-productivity tools has arrived for their consideration. We call these products the new productivity platforms and define them as:

Platforms that speed application delivery and ongoing evolution through: visual tools, hot deployment and continuous innovation, built-in administration and management, and active participation of business experts in application delivery.

We've found 22 products — a surprisingly large number — that fit this description. Nine of these platforms — Appian, Aptify, ClaySys Technologies, Cordys, expanz, LongJump, OrangeScape Technologies, Servoy, and WorkXpress PaaS — provide broadly applicable environments. The remaining options we've examined are each best for certain types of applications. The full list of products we studied is:

 

 

The new productivity platforms are successors to the fourth-generation languages (4GLs) of the '80s and '90s. Like those environments, the new productivity platforms seek to simplify design and creation of applications. But the new productivity platforms also address the problem of productive application delivery more broadly by accelerating the entire application life cycle, equipping many roles in the application life cycle, and empowering business experts to deliver applications.

The new productivity platforms seek to make the entire application life cycle move faster. They begin with initial design and development but then proceed through deployment and management to support of continual updates (what we once called application maintenance). The acceleration starts by reducing the amount of infrastructure configuration and coding developers must do to deliver an application. New productivity platforms allow developers to:

  • Focus on the business problem, not the infrastructure details. Customers using these products uniformly praise them for eliminating chores not directly related to solving business problems. The new productivity platforms eliminate deep coding to middleware application programming interfaces (APIs), deployment descriptors, and build scripts as well as related coding for software packaging, software deployment, and platform configuration.

    Some of the new productivity platforms promise "zero code development." Ignore the phrase. The new productivity platforms only rarely eliminate the need to write at least some code for real applications, though in most cases, developers can build their projects with comparatively little conventional coding. And when a platform requires coding, that coding is usually in a higher-level dynamic language rather than Java or C#.

  • Create and change applications as needed. Most of the new productivity platforms employ an underlying technology we call metadata execution to provide great flexibility in designing and maintaining applications. Simply put, the tools output definitions, not code, and the definitions are then interpreted by the platform to create the running application. Metadata definition is far more flexible than code generation, the productivity technique that preceded it.The ultimate test of an environment's flexibility is the developer's ability to change an application's data schema without needing a database administrator and without breaking the application. Most of the new productivity platforms pass this test. Integrated impact analysis testing is one technique that provides this level of flexibility.

  • Implement new applications and changes quickly. Most of the new productivity platforms employ automatic deployment, which also speeds the life cycle. Rather than procuring, installing, and configuring a platform stack for the application and then building the application for installation and configuration on that stack, developers automatically deploy their projects.

    Again, metadata execution is crucial: Because the metadata definitions are installed into an interpreted engine, they can also be deployed automatically. Several of the new productivity platforms apply this technique both to on-premises and public cloud environments (and some just to clouds).

The primary risks of the new productivity platforms: You get stuck on a proprietary platform with no way forward, you write a lot of custom code anyway because the platform doesn’t meet enough of your application needs, or you don’t realize expected productivity gains due to your own failed processes or inadequate vendor tooling.

How will you meet the challenge of the AD&D crunch? Certain projects will require very agile conventional coding, but you could also shift many projects to one of the new productivity platforms. As you strategize to meet the challenge of fast delivery, we recommend that you add one of the new productivity platforms to your strategy. We've found enough evidence that these platforms can speed delivery to be convinced that the category presents major opportunities to AD&D shops. The oldest vendors in the category have supported some very impressive work. The risks associated with these platforms are readily understood — and most AD&D shops understand how to evaluate platforms and the vendors that provide them.

As always, we very much appreciate your comments. For more detail on the vendors we studied, see the companion spreadsheet for this report at this link: http://www.forrester.com/rb/Research/new_productivity_platforms_our_interactive_vendor_profiles/q/id/60967/t/2. (Note: Pay wall.)

This research includes an experiment. The vendor spreadsheet included with the report is part of a "research collection" that I can expand over time. I'd like to expand the collection in at least three ways. First, add screen shots from more products that fit into this broad category so we can see more of the innovative ideas out there. Second, add products that look promising. (I've just been introduced to Blue Prism, for example, and think it belongs in this research.) Third, add stories about real-world experience with these products. Will you help me by leaving me your suggestions and stories as replies to this post?

Comments

Developer versus business users and MOBILE

John, great coverage on an important direction for systems of engagement. You make an excellent point about life-cycle management. It is imperative that the RAD platform does not require outside Java or C++ coding as it otherwise can turn into the problem of synchonization at deployement time. Also integration with content capabilities of MS-Office are such problems, which is why we have those integrated natively and managed throught the same lifecycle. Just because we have that does not mean that the ISIS Papyrus capability is only suited for Composite Content Applications. MS-Office can also not be used for high-volume content or on Unix, Linux or Mac servers or frontends or for Mobile. What you did not make as clear, even though it is implied, is that the development problem is multiplied by the need to deploy those applications to MOBILE as well. Papyrus application can be deployed one-to-one to iOS and Android devices without any additional coding, and it is not through a HTML browser presentation. Many functions are also available in offline mode, but clearly interactive processes require connectivity. User empowerment by such platforms is still a novelty and most business do not know how to handle that. It is also necessary to consider the adaptability when the application user interface is deployed. Some are well suited to user modifications and others aren't. We would not consider that something to be enforced the same way across all businesses.

Each business has a different perspective on what facilities should be made available to business users for application creation or modification. Simple role authorization can control adaptation functions for each user. We find that the ability to create and adapt new user interactions (forms, content, wizards and processes) is widely used. That includes the ability to write sphisticated Natural Language Rules without the need for user training. SOA (SILO or Cloud) backend connectivity is provided as IT-defined service tasks that user can pull into all apps. Thanks again!