Ok. You read my last blog post and built your first your mobile app for iOS and Android. You’re happy. Happy as a clam. You leveraged your Java expertise, didn’t have to learn a new OS specific language and deployed your mobile app to iOS and Android. It’s not $WhatsApp that FB just paid $19B for, but cheers for you!
Now your manager comes in, tells you what a great job you did on that app. Folks really like it… but now he wants you to expand it further. He wants new mobile apps that reach the main servers – where the mission critical apps live. Can you do that? We’ll need it to:
- Build an app to access the existing enterprise applications like PeopleSoft, Siebel, etc. We can’t afford a rewrite, but the execs want to mobile enable them to the field
- It has to be secure. Enterprise grade. Proven. No compromises here.
- SLAs (service level agreements). It needs to perform, and the apps performance needs to be measured, with reporting so we can see how the app is being used
- Caching. We don’t want to keep hitting our infrastructure unnecessarily. For the static data, there’s really no need to keep retrieving the same data over and over again when we can simply cache it, right?
What do you think? Can you do it?
Check out this post by Jeff Davies covering mobile apps and Oracle Service Bus, part of the new Oracle Mobile Suite – and get happy!
To learn more about Oracle Mobile Platform, click here.