Internet technologies have made it possible for organisation to expand reducing time to market for new products and services. The internet has been great but the main advanced here is being pushed by the HTTP. Some might disagree but the majority of communication between web and mobile applications is over HTTP protocol. HTTP is not the only protocol for the internet but it is the main enabler. One way to consume the HTTP protocol is via a web browser. As a developer and architect, your options are limited when it comes to building an application for the browser. We will get into some of the limited choices later. We will take a look at the frameworks available from a Java language vantage point. This article does not discuss what framework is better than…. This choice is left to your team. There are many points to consider when selecting a web framework for your project but we will restrict ourselves to following few:
It must be said that the most important aspect of a software project is to consider its users. How would they interact with the application? This blog article is focused on the web and will not go into discussion about standalone desktop applications.
The way the software is delivered to its end-users would have a major impact on deciding how to implement the software, at least on the user interface.
Here are some choices:
There are three main factors to consider here: time, cost and resources. Thus, the program lead would have to ask himself the following questions:
Answering the above questions would provide some clarity on what to do. Also, when choosing a framework, do check its maturity; how often is it updated and how big is the community supporting it. Do not let the hype cloud your judgement.
Just tell us about your project, what are your goals, and let's start.