I try to reply to all ... > In terms of a mobile client, what sort of functionality would you like to > see or have you envisioned for it?
I think that the mobile client should permit the basic operations (create, edit, invite ...) and should also permit to store and handle a multiple connection to different servers (federations ?? is it the right name?) and some functionality based on geo-location. The main problem with iPhone development is the "closure" to third-part frameworks and library also (for what I can understand at the moment) the only way to develop an iPhone native client application is using HTTP Protocol isn't it? do you think it is possible to develop a client using the HTTP protocol and not the Python or Java client library? Once give an answer to those questions further point should be discussed with iPhone development, to publish iPhone application on the App store an iPhone developer account is needed and ... it is not free (99$/year) also for free available applications. For Thomas > I'm working on a mobile android wave client, Do you think we can share the same software requirements document? > Also, yes, mobile clients need to be designed with both lag and even > offline access (cacheing/sycning) in mind. uhm... are you sure? why? I think that a mobile client shall require a connection to work, like a browser... -- Giacomo
