Hi... On 1 Feb 2016 02:05, "Rémy Sanchez" <[email protected]> wrote: > > Hi all, > > I'm currently considering to use Tryton for a client. >
Great to hear, it's a solid platform for business applications > They have quite advanced needs for an ERP, and more specifically they expect a mobile app that allows on-the-ground teams to interact with customers in ways I am not sure Tryton can handle. Tryton has a pretty good and growing set of modules for common ERP functions, but its potential is greater if you think if it as a "business application framework". If you are willing to do some module development you can do most anything and achieve seamless integration with the standard modules. > Namely: > Get items in/out of stock using a bar code scanner The standard stock modules are fine for this; all that is missing is the interface. The simplest is to use a web page front end with flask-tryton or with nereid for more complex web apps. A simple one page web interface with flask would be fine. > Have their clients to sign for deliveries directly on the device See above. A signature could be captured and saved as a bitmap attachment to a shipment record for example but there are other digital signing mechanisms too. Not sure of the requirements here. > Visualisation of data on a map This would be the most work, but PostgreSQL does GIS well and there are APIs to hook into google maps and open street maps. Not sure what native client or SAO have to offer off the shelf though > Integrate with phone agendas Tryton has calendar and DAV so this should be doable > Statistics dashboards/excel exports Tryton is pretty capable here. It would use ODS not XSLS. But excel can use open document format files. The native and SAO clients have some dashboard-like capability but look at the flask-tryton or nereid options for more flexibility > Given those requirements, I guess that Tryton would merely be a RPC/database server and would require me to develop 100% of the UI? I would say tryton would provide much more because it handles all the business logic too. Plus you don't need to develop a full front end. You would have more success with using SAO for 80% and smaller scope web apps for the 20% that can't be done by the standard front end. > > I'd love to hear from your insights. > > Thanks, > Rémy > > -- > You received this message because you are subscribed to the Google Groups "tryton" group. > To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/f299556f-186e-4805-9ed7-1ae57a916c88%40googlegroups.com . -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/CAJ0%2BmOpe5GiRoWi3FvAL9rbFhboUuNWBYqB-zqKNp-Psuky6pw%40mail.gmail.com.
