Doorgaan naar hoofdcontent

Mobile is Hot ! But be aware ...


I see it in a lot of projects but also I see that it is handled just like testing in the beginning: "oh we estimate some extra days and we also go Mobile !"

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.

OpenText Assure

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

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.

Conclusion

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.
Labels:

Reacties

Een reactie posten

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h
12 reacties
Meer lezen

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .
48 reacties
Meer lezen

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept of servin
5 reacties
Meer lezen