Hi Jian, It's great that this project drive so much attention :) I will copy/paste what I told Manish since you are interested in the same project: We mostly discuss projects here so no need to contact me directly. What is in https://github.com/xwiki-contrib/android-authenticator is mostly a not finished crappy POC aiming at the following goal: 1) Provide a reusable standard Android authenticator that any application would use to communicate with an XWiki instance. The same way many applications propose you to reuse the registered Google accounts for example. It must be as safe as possible (no clear password given to all application asking for it for example :)). 2) As both an example of how to use this authenticator and a very useful tool, implement a synchronization adapter which will be in charge of: ** putting all (or a configurable subset of) the users from the wiki in your Android contacts and automatically update them ** (nice to have) allow modifying those Android contacts and send the modifications to the wiki There is a lot of stuff already started but should not be taken as granted and at the end the result should be: * well documented (especially what an application author should do to use that connector properly but also for anyone that want to continue working on it) * have automated tests * easily built without something like Android Studio (probably graddle which seems to be the new standard in Android world. XWiki is mainly using Maven right now and Maven have Android plugins.), it will also need to be automatically built on http://ci.xwiki.org Of course the plan is to have it on Google Play Store at the end :) Feature wise this project is not very big (and it's already started) but the most important thing is to be as standard and integrated as possible and easy to use for applications that would want to manipulate an XWiki instance. Your proposal should details what you plan to do, what Android version your are targeting (should support version as old as possible since latest version are far from being as common as application authors would like them to be :)), etc. On Tue, Mar 1, 2016 at 9:35 AM, Jian Guo <aliezted(a)gmail.com> wrote: -- Thomas Mortagne