Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL.
Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :)
Version: 1.0.0 (Android)
Severity: normal
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T35428 Add photos to articles | |||
| Declined | None | T39877 feature suggestion: save articles or bookmarks online | |||
| Declined | None | T35856 Wikipedia Android App 2.0 release (tracking) | |||
| Invalid | None | T33979 Photo upload in mobile app using PhoneGap's Camera interface | |||
| Invalid | None | T35859 Commons uploader | |||
| Declined | brion | T33458 Authentication support for Android app | |||
| Resolved | yuvipanda | T33497 Android app should support (or always?) use HTTPS | |||
| Resolved | None | T33333 No SSL for MobileFrontend m. domain: https://en.m.wikipedia.org/ does not respond | |||
| Resolved | Reedy | T33335 Rename wikis with multiple subdomains | |||
| Resolved | None | T40763 Our *.wikimedia.org cert doesn't properly cover https://pa.us.wikimedia.org/ | |||
| Resolved | None | T66977 https://wg.en.wikipedia.org is using an invalid certificate |
Should we just go ahead do this for 1.0? Just a URL change, or are there other potential issues?