Re: [Health-dev] Androit application for Gnu Health

[mdiouf]

Hi All,
Luis nice idea for the POC.
If the need was for commercial online sales app, with simple scenarios, 
definitly I'll choose Web app with Flask or Django or something like. But in my 
head the App had to be very functional, like allowing nurses taking pictures or 
videos directly, being notifyed directly when results of an analysis or new 
events are available, not connected mode, ect.
My company can provide resources for Android. If others are ready also for 
working for a web app version, it must be taken into consideration.

Thanks

Cordialement,
Baamtu: Imaginez et ensemble nous réalisons.
Mohamed Moustapha address@hidden Général Baamtu SénégalCTO Baamtu France
Tel (FR): +33 6.03.84.29.76
Tel : +221 77.552.21.42http://www.baamtu.com



>---- Original Message ----
>From: Luis Falcon <address@hidden>
>To: "Cédric Krier" <address@hidden>
>Cc: address@hidden
>Sent: Lun, Dec 8, 2014, 10:46 AM
>Subject: Re: [Health-dev] Androit application for Gnu Health
>
>Hi Cedric, Chris, Mohamed, Anousak and team
>On Mon, 8 Dec 2014 09:41:06 +0100
>Cédric Krier <address@hidden> wrote:
>
>> On 07 Dec 19:49, Chris wrote:
>> > I think there are reasons to develop both. With good, robust design
>> > (like with Bootstrap), webapp UX on a mobile device is great, so the
>> > flask-tryton is awesome (and the other flask addons that make
>> > UX/webapp design easy). However, there are some bonuses to an
>> > Android app. For example, asynchronous interactions (e.g.,
>> > poor-connectivity environments) is somewhat easier, I think, to
>> > develop in Android.
>>
>> asynchronous is not only possible with Android, it is prefectly
>> possible with web app.
>> But asynchronous client is very difficult to implement correctly and
>> they generate a lot more difficult case to manage like update conflict
>> etc.
>I think I could we could work on Proof of Concept taking a simple
>scenario, such as recording vital signs.
>We could try it in both platforms, and see what would be best in the
>medium and long term.
>
>If the web app is functional, then I would leaning more towards
>the flask solution, since it would be platform independent. In any case,
>I'm open to any.
>
>Let me know your thoughts
>
>Best
>
>> But there is already in Tryton the CardDAV and CalDAV support that are
>> designed to also work asynchronously (but that's part of the
>> specification).
>>