We have delivered mobile applications which are in production with the help
of Ionic framework (http://ionicframework.com/ ) on top of OFBiz .
Experience so far is good and ionic community is really active , growing
and helping community.

As Ean mentioned, " *you no longer render pages on the server and send them
to the client. **To behave like an actual "app" you need to approach it as
a program written in Javascript that renders HTML interfaces locally and
communicates with the server using a combination of JSON-RPC and REST.* "
This is really important point here when you are building mobile apps.

Jacopo also have done  improvements in OFBiz, with the help of them  you
can call OFBiz out of the box services and events as APIs . Services and
events are able to accept Json and return Json in OFBiz which will help you
to build mobile applications on top of OFBiz.

Thanks
--
Divesh Dutta.

On Wed, Jul 29, 2015 at 1:22 AM, Ean Schuessler <e...@brainfood.com> wrote:

> The trouble with AngularJS is that they have a terrible case of NIH and are
> re-inventing all the existing popular patterns like IOC, dependency
> management and observer style data change events. In the 1.0 version they
> were dismissive of problems like dependency management and let rediscover
> the pains of not being able to fractionally load their infrastructure even
> though it has been a solved problem for tools like RequireJS for a long
> time. Now the roadmap for AngularJS 2.0 is so different from 1.0 that it
> might as well be regarded as a different product and there is also real
> cloudiness around the relationship between AngularJS and Polymer. Google is
> developing both so the "it's made by Google" argument that usually puts
> wind in Angular's sails isn't applicable.
>
> On Tue, Jul 28, 2015 at 10:11 AM, Ron Wheeler <
> rwhee...@artifact-software.com> wrote:
>
> > Good analysis.
> >
> > I wonder if Ionic is a good choice for a portable mobile framework.
> > http://ionicframework.com/
> >
> > One does not want to get tied up in low level support for all the flavors
> > of mobile devices.
> >
> > It is open source and supports AngularJS which seems to be a good model
> > for building Javascript applications,
> >
> >
> > Ron
> >
> >
> > On 28/07/2015 10:25 AM, Ean Schuessler wrote:
> >
> >> The real difficulty is that if you want a genuinely mobile app and not
> >> just
> >> "mobile web" then the approach has to completely switch. With a Cordova
> >> app
> >> you no longer render pages on the server and send them to the client. To
> >> behave like an actual "app" you need to approach it as a program written
> >> in
> >> Javascript that renders HTML interfaces locally and communicates with
> the
> >> server using a combination of JSON-RPC and REST. This would represent an
> >> enormous refactoring of the entire interface but it would open whole new
> >> horizons from a UI perspective. David has made some real improvements to
> >> handle REST in Moqui's version of the control servlet that we would also
> >> need to bring in (ie. you can bind services to a combination of URL and
> >> HTTP method).
> >>
> >> On Wed, Jul 8, 2015 at 11:13 AM, Pierre Smits <pierre.sm...@gmail.com>
> >> wrote:
> >>
> >>  Hi all,
> >>>
> >>> There are a lot of mobile specific development frameworks out there.
> >>> There
> >>> are even a few projects under the ASF umbrella that cater to that need.
> >>>
> >>> What would you consider the best solution to pair OFBiz with? Of are
> the
> >>> capabilities it delivers sufficient?
> >>>
> >>> Please share your thoughts.
> >>>
> >>> Best regards,
> >>>
> >>> Pierre Smits
> >>>
> >>> *ORRTIZ.COM <http://www.orrtiz.com>*
> >>> Services & Solutions for Cloud-
> >>> Based Manufacturing, Professional
> >>> Services and Retail & Trade
> >>> http://www.orrtiz.com
> >>>
> >>>
> >>
> >>
> >
> > --
> > Ron Wheeler
> > President
> > Artifact Software Inc
> > email: rwhee...@artifact-software.com
> >
> > skype: ronaldmwheeler
> > phone: 866-970-2435, ext 102
> >
> >
>
>
> --
> Ean Schuessler, Brainfood Co-Founder
> e...@brainfood.com
> 214-720-0700
>

Reply via email to