--
You received this message because you are subscribed to the Google
Groups "OBIEE Enterprise Methodology Group" group.
To post to this group, send email to
obiee-enterpri...@googlegroups.com
To unsubscribe from this group, send email to
obiee-enterprise-met...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/obiee-enterprise-methodology?hl=en
All content to the OBIEE EMG lies under the Creative Commons Attribution 3.0 Unported License (http://creativecommons.org/licenses/by/3.0/). Any content sourced must be attributed back to the OBIEE EMG with a link to the Google Group (http://groups.google.com/group/obiee-enterprise-methodology).
but when Oracle comes and does a license review and they see that the
Mobile Apps Service is running be ready with your checkbook.
-w
--
The primary difference is that Oracle takes a "build once, deploy everywhere" mentality, where Roambi is about building new views that really take advantage of the multi-touch UI using OBIEE as a back-end data source. Oracle's approach will require less implementation - you can get up and running on mobile faster and the UI will be (largely) consistent between the browser and the mobile device. With Roambi, you have to spend time building new content, but that content will likely be received better by certain types of user audiences. Roambi's views are fixed, though, so if you run into a requirement that can't really be addressed by Roambi's views, you're stuck.
--