Separate front-end sounds fine. Use a REST architecture with JSON as the data exchange format. I'm pretty Spring MVC supports this through the use Jackson JSON library. Its something to add to your list of possible options.
On Wed, Jan 18, 2012 at 2:38 AM, nazeem <md.naz...@gmail.com> wrote: > Hi > > I am currently developing an application using Wicket + Spring + Hibernate. > So far everything is smooth and I use a lot of Ajax which works perfectly > fine. Now I need to provide options for data entry via mobile devices like > Andriod (Samsing Tab) + iOS (iPad). My initial plan was to develop web > based UI specific to suit these devices so that it reduces the complexity > of > developing for multiple platform. But now, I need offline usage as the > signal strength can vary from place to place, so web based option is ruled > out. (not sure if options like gears for offline usage will work in mobile > devices). > > Also I need to use device specific native features like camera to upload > photos from the device. So I am planning to develop separate front end for > iOS & Andrioid. Is this the right approach ? > > What will be the communication layer between Server & Mobile applications ? > REST ? If not what else. Please suggest. > > Also advice on the libraries that will help me get there.. > > regards, > nazeem > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/wicket-appl-architecture-tp4305917p4305917.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
