Jump to: navigation, search

Difference between revisions of "RAP/Mobile Browser"

< RAP
m (RAP/Mobile moved to RAP/Mobile Browser: prevent confusion with "RAP mobile" project)
(RAP on Mobile Device Browsers)
Line 1: Line 1:
== RAP on Mobile Device Browsers  ==
+
With the increasing popularity of smartphones and tablet-PCs it's also important for RAP to support and adapt to these platforms. Since modern web-standards like HTML5 are supported by modern mobile devices, they offer a possible solution to write cross-platform applications. RAP can offer a powerful solutions for such scenarios, allowing to write complex business-applications for modern mobile devices, provided a appropriately fast internet-connection is constantly available.
  
With the increasing popularity of smartphones and tablet-PCs it's also important for RAP to support and adapt to these platforms. Since modern web-standards like HTML5 are supported by modern mobile devices, they offer a possible solution to write cross-platform applications. However, writing cross-platform conforming javascript and HTML is complicated and not very comfortable, especially for developers used to powerful IDEs and debugging-tools. RAP can offer a powerful solutions for such scenarios, allowing to write complex business-applications for modern mobile devices, provided a appropriately fast internet-connection is constantly available.
+
There is a common look and feel, as well as certain features, that most mobile applications have in common, even across different platforms. RAP should, within its capabilities, aim to conform to those. As of RAP 1.5, support and features for iOs is mostly solid, while Android still has some more severe issues. This is partially due to some bugs of its default browser that are hard to work around. Other devices have not been tested. ''Due to emerging alternatives, improving support for mobile browser further is currently not a main focus of RAP core development.''
 
+
There is a common look and feel, as well as certain features, that most mobile applications have in common, even across different platforms. RAP should, within its capabilities, aim to conform to those. As of RAP 1.5, support and features for iOs is mostly solid, while Android still has some more severe issues. This is partially due to some bugs of its default browser that are hard to work around. Other devices have not been tested. ''Due to emerging alternatives, support for mobile browser is currently not a focus of RAP core development.''
+
  
 
An overview of mobile-related bugs can be found in [https://bugs.eclipse.org/bugs/showdependencytree.cgi?id=323031&hide_resolved=1 bugzilla].
 
An overview of mobile-related bugs can be found in [https://bugs.eclipse.org/bugs/showdependencytree.cgi?id=323031&hide_resolved=1 bugzilla].

Revision as of 10:34, 24 May 2012

With the increasing popularity of smartphones and tablet-PCs it's also important for RAP to support and adapt to these platforms. Since modern web-standards like HTML5 are supported by modern mobile devices, they offer a possible solution to write cross-platform applications. RAP can offer a powerful solutions for such scenarios, allowing to write complex business-applications for modern mobile devices, provided a appropriately fast internet-connection is constantly available.

There is a common look and feel, as well as certain features, that most mobile applications have in common, even across different platforms. RAP should, within its capabilities, aim to conform to those. As of RAP 1.5, support and features for iOs is mostly solid, while Android still has some more severe issues. This is partially due to some bugs of its default browser that are hard to work around. Other devices have not been tested. Due to emerging alternatives, improving support for mobile browser further is currently not a main focus of RAP core development.

An overview of mobile-related bugs can be found in bugzilla.