In our last post of this series, we saw the need for modularity and flexibility. We will look now at how a platform should not only deal with the server side but also with the client side.
Supporting More Than Just the Server Side
Frequently, developers, architects and project managers evaluating enterprise applications focus on the server side features of the architecture. They examine how business data persistence is implemented, how business logic is designed and what APIs are available for integration. However, client side features are just as important as the server side. When evaluating an ECM platform, it is important to consider more than just the core capabilities encompassed in server-based components. Architects should also ensure that the platform does not impose excessive restrictions on the user interface the end user will leverage to access the application content delivery and/or the content delivery of the content itself.
ECM platforms should easily support multi-channel content delivery and interaction. This capability is growing even more critical as businesses increasingly embrace mobile devices, tablets and other tools in addition to browser and rich-client applications that run on P.Cs. Ideally, the platform will provide or allow integration with one or more presentation frameworks to support rapid application development:
A range of different web user interface frameworks for different interaction use cases (e.g. JSF, GWT, basic web templating, etc.) to ensure all kinds of web applications, including mobile and tablet based user interfaces, can be served in the most appropriate manner
R.I.A. (Rich Internet Applications) frameworks supporting Flex and related middleware such as Adobe Life Cycle or Granite DS, to ease the development of these interfaces
“Silent Applications” for scripting and batch processing purposes
Thick mobile applications, supporting major technology such as Android and iOS, and providing dedicated SDKs to wrap the platform services and APIs.