Of course this is not the case, it can be a project on its own.
There are a lot of choices to be made, some of them are:
- Which mobile platforms do we have to support?
- What are the performance requirements?
- Do we want to develop once, run anywhere?
- Do we want to use native functions of the mobile OS?
What I also see, is that more and more BPM/Integration platforms are going to support it.
But then again the Mobile experience is somewhat different than the Browser (and Desktop) experience.
So depending on the requirements of the Mobile App, the platform can suffice or not.
I will shortly describe some platform examples.
This is a BPM platform that supports Mobile. However the UIs are running within the browser app of the mobile device. The advantage is that it is developed once, and runs on the desktop and iOS, Windows and Android mobile devices. The consequence is that no native functions can be used.
OpenText Process Suite
This is a BPM platform that supports mobile application development. The following picture gives an architectural overview.
The architecture uses some open source frameworks to implement mobile apps.
Oracle ADF Mobile
Oracle Fusion has extended its Fusion stack with ADF Mobile. This framework is also based on open source frameworks.
Tibco Silver Mobile
This is a development platform to develop mobile apps. It adheres to the principle develop once, run anywhere.
Windows has several development environments for mobile development. Windows has a Windows Phone SDK and also introduced a web based development environment: Windows Phone App Studio.
Of course these tools are all for the Windows Phone.
The development of Mobile apps must not be taken lightly and must sometimes be seen as a separate project. Most of the platforms in the field have separate development environments for it and can be developed as separate apps next to the normal UIs.