The way that we work is we try not to look at the gaps at the very beginning. A customer says, this is what we need, this is our back office and we've chosen Oracle to do that. We try not to get over excited at the beginning about how we could possibly take that forward later. Let's move them to cloud, let's get them to get those advantages straightaway. Then very quickly you start saying, well what things are still slowing you down? What are the manual processes that are happening in your organization?

You know the word "manual" is the big trigger. They say well, we're still doing this on a spreadsheet, and we're still doing this. I just send emails out to these list of people, where I say, okay, that's an area where I want to take it and automate it, and that's where I want to extend my application.

We didn’t really have any previous solution. We just started with this one.

We did not use a different solution before.

I have tried native mobile app SDKs for different OSs, but there is a big learning curve to start development with them, and an app built for one platform can't be ported easily to other platforms. We chose MAF because it has out of the box support for data visualization components, and offers an easy and declarative way to perform development.

I used other frameworks such AngularJS and Ionic as they are free.

I used iOS Cocoa Framework. I chose to move to MAF because I work with Oracle in general, and MAF looked like a great framework to work with.

Oracle Mobile Application Framework was the first solution of this type we tried.