Talk:List of rich Internet application frameworks
|WikiProject Computing / Software||(Rated List-class)|
Revisiting the Article Title: List of rich internet application frameworks
I want to help with this content regarding platform-independent application platforms. Each of the products/platforms in the current grid allow web developers to produce applications that run and behave as native applications on a variety of desktop and/or mobile platforms.
There is clearly critical mass in this category as the pendulum swings back to native apps from pure browser based apps that were championed as part of the customer adoption trends Web 2.0 and SaaS. Adobe AIR, Sun Java FX and Microsoft Silverlight are huge players driving these solutions for the desktop. Appcelerator Titanium, Nitobi PhoneGap and Rho's RhoMobile lead a pack of up-and-coming products that address mobile alonge with desktop solutions.
Discussion, please, so we can confidently move forward.
- I think that your title is better.
The changed title would be misleading, many other things could also be considered multi-platform. For example, anything in Pure Java, and C++ that only uses cross-platform libraries.
An additional framework: local Web server running PHP
Rich Internet applications can be built easily by running a local Web server, such as Apache, or one of the many tiny and faster alternatives, such as Mongoose, as the operating platform. Then the application itself is written in a server-side language, such as PHP. No sandbox, Ajax or other security workarounds are needed, as such a setup has complete access to the local machine's operating system and file system (as complete as any executable file). The user interface is naturally browser windows and tabs, although the browser can be made to generate standalone windows easily.
The principal drawback of this methodology is the rather severe security precautions enforced by most browsers on local operations the first time such applications are run: the user must click at least one obscure warning button to permit operation, or else the application must run in HTTPS using a trusted certificate, which costs a significant amount of money. Just as with executable files, too, malware and viruses are significant risks for the end user.
Another drawback, if the application is to be used by other computers on the Web, is the need to make the local computer visible on the Web. This may involve registering its domain name, tracking WAN IP changes by the ISP, and making NAT or Firewall entries in the local Internet router or wireless adapter.