An interesting experiment with JSON, Postgres and Omnis
Vik Shah
Vik at Keys2Solutions.com.au
Mon Jan 16 20:59:11 EST 2017
Hi Clifford,
>
> I'm curious what has you think you need a RESTful API. What is your use case? I'm not arguing that you should or shouldn't need one. If you expose a RESTful API, how do you intend to display the JSON or XML that Omnis returns?
>
I’ll give my own account here,
1. Omnis Studio 5.x/6.x/8.x all those versions have a fixed screen size and the number of new devices with different screen sizes are growing by the hour.
2. Omnis JS is a bit on the heavy side.
3. In my experience, I have found that the Omnis JS application consume the battery quickly than other web apps. I may be pointing at the way I may have coded the application but nonetheless the equivalent HTML5 app was performing better than the Omnis JS.
4. Device functionality integration. While the team at Omnis is going as fast as they can with device specific feature integrations the open source community is travelling at blinding speeds.
5. frontend extensibility, Omnis JS is within the realm of Omnis family, but using widely accepted frameworks means that there are more chances to get cheaper developers should the client require any changes/extensions made to the web app.
The JSON retuned from Omnis is consumed by the HTML5, jQuery framework and the information displayed on an screen size agnostic layout, one of the wonders of having bootstrap.
Vik Shah
Director
Keys2Solutions
AU: +61 411 493 495
SE: +46 21-495 01 05
US: +1 (415) 413 4172
More information about the omnisdev-en
mailing list