= Android/BOINC development items =

[[TicketQuery(component=Manager - Android,status=new|accepted|assigned,order=priority,format=table,col=summary|status|component|owner|reporter|priority)]]

Some remaining development tasks.
Please contact me (David Anderson) and post to boinc_dev if you want to help.

=== Feasability of GPU computation, e.g. LG Nexus 4's GPU Adreno320 supports openCL 1.2 ===
Google seems to push RenderScript over openCL support on Android...

=== Higher resolution project icons and slideshow images ===
Icons and slideshow images are not ideal for high resolution screens.

=== Statistics ===
e.g. run time, finished tasks, etc.

=== Badges / Achievements ===
* supplied by project and/or local based on statistics
* shareable on social media

=== Attach Wizard ===
Feedback indicates that users are not happy with having to register with every project separately.

Initial proposal of UI flow: https://www.fluidui.com/editor/live/preview/p_xuIwayLOet0gFoFlBHZJtpmbqnxF5Z7O.1394002154909
1. splash screen
2. if no project attached, prompt credential input. this screen can accommodate Google sing in later.
3. project selection. multiple choice. project info screen opens with (long) click on project
4. attaching. using previously supplied data. tries login, if fails, try registration. give users introduction/hints in the mean time.
5. successful. if no conflict.
6. conflict resolution. one screen for every project that returned "bad password" (account exists but password is wrong). give user a change to correct his data (name or email if not users account; password if user registered before with different password), only for this specific project.

Store user data to pre-populate fields in further attaches.

Concerns with initial proposal:
* Users that already have different accounts with various projects or prefer having separate id-password combinations with all project accounts
-> offer to supply login information separately for each project. add button to screen 2. possible to pre-populate name/email field from previous data.
* Storing the users password for further attaches raises concerns
-> add checkbox to screen 2 to opt-out
-> or do not store password in general. require re-type if further attaches and later point in time.
* Conflict resolution needs to be adapted based whether project uses name or email as identifier
-> "uses_name" attribute allows distinction
* WCG does not allow registration on client. Treat separately.
-> prompt screen that forwards users to WCG homepage.