The mobile choice
Going Mobile
You want to build your new web application, but suddenly you understand that your users might access it from their mobile (smartphone or tablet) devices, what do you do?
Mobile is everywhere
If you haven't been living in a cave for the past few years, you should know by now that the world has gone mobile. Maybe your applications are not yet coping with the changes happening out there, but that doesn't mean that your users are not eager to embrace those changes. The mobile demand is growing everywhere, and the enterprise world is not going to escape it. Checkout this tablet usage states and figures cheat sheet if you still need to convince yourself.
What does that have to do with your applications?
Nowadays every user expects a website experience to be consistent regardless of which device they use to access it. If you're not delivering that experience, your users might be having a hard time with their mobile devices.
Let us help you
If you have application requirements that  can only solved by doing a native application, then you can use the OutSystems Platform to create the services and data backend for it

On the other side, if you're building a typical enterprise application and you want your users to use it on their tablets or smartphones then you have more options:

Do you need the application to be distributed by the application store? (e.g.: App store on iTunes)
If yes, then you need to build a hybrid application. The current policies demand that some part of your application is built using native code. That is the only way it will be accepted and placed on the marketplace, even if it is a free application. Of course it can still be rejected for any other reason, depending on the store criteria.

Do you require any hardware integration? (e.g.: Camera access, to take pictures)
Using the device's hardware is not limited to Hybrid or Native applications; with the use of HTML 5 you can still use some of the device's features. Before opting for a technology, double check if the requirements that you have can be fulfilled with just HTML 5 or javascript. If not, then the decision is only between a Native or Hybrid application.
Responsive vs Smartphone specific
The main difference between tablets and smartphones is the available real estate, which can really be a constraint when designing applications for smartphones. To deliver a great experience on smartphone applications you should consider building a specific application for those users.
Building a smartphone only web application
You can build an application that adapts itself the multiple devices your users might have - responsive design - or you can decide to build a specific interface for those devices, for example, smartphone only applications. So why not always opt for Responsive Web Design? It's a matter for compromise. If you build a specific tailored application for the smartphone user, you can take advantage of that and re-think all screens, optimizing them for that specific scenario. When it comes to larger devices such as tablets, the responsive approach is, by default, the best option as these devices have resolutions close to standard regular displays (e.g.: 1024x768).
How to build a Hybrid application?
To build a hybrid application you need to use a third party tool such as PhoneGap Builder. There is an excellent How-To in the OutSystems community for building hybrid application using the PhoneGap application that you should definitely check.
Choosing the best solution
Before you start building your mobile applications, you should first understand what it takes to go mobile and what options do you have. The first choice you have to do is selecting the type of technology that will be requiring for your case: Web, Hybrid or Native.
Click here to see your activities