Is RAP a good fit for mobile applications? RAP as you know it uses HTML5 for rendering the user interface. But in our experience, browser-based apps still feel a bit clumsy on current mobile devices. So we went a step further and enabled native clients to render SWT-based UIs on mobile devices.
After Google's acquisition of Instantiations, WindowBuilder (winner of the 2009 Eclipse Community award for Best Commercial Eclipse Tool) was contributed to the Eclipse open source community (http://www.eclipse.org/windowbuilder) and is now a thriving open source project. Now the most powerful Java UI builder in the world is freely available for any Eclipse developer to use and extend. In this session, we will show you how to use WindowBuilder to create and edit SWT, Swing, GWT and Android apps and also show you how you can get involved in the project.
Developing mobile applications is a challenging task, especially given the ever-growing number of mobile platforms, devices and form factors. Implementing an app for just one platform just isn't an option for many enterprises if they want to reach as many clients as possible. In this session, I will give a brief overview of the main approaches for developing cross-platform mobile applications. We'll start with native apps, and work our way through hybrid applications and interpreted apps to HTML 5 based solutions.
Improving software quality is a continual goal for developers. Static analysis is an easy technique to employ throughout the lifecycle. Mobile developers must be aware of the way different devices can exploit missing or malformed resources. The MOTODEV team has created a free Eclipse-based static analysis tool that can be updated quickly each time a new Android platform is released and can be customized by third parties to create their own validation sequences.
