geoloqi / geoloqi-iphone Goto Github PK

in addition to the separate sections for palm, android, iPhone, mobile web, etc. there should also be a section for features/bugs/issues that pertain to all the mobile clients. for instance, the feature request issue i just filed under iPhone for including OpenID in the initial sign-up/OAuth screens, should be for all mobile clients and would be filed in that github section for geoloqi, if such a section existed. also, this issue itself should actually be filed under all mobile client issues, not just iPhone, if such a section existed (although that would be a rather confusingly recursive request, as you would be requesting the addition of the section in the section that already existed).

this is primarily because the geoloqi wiki feature spec has a specific section containing features & spec for all the mobile clients —> http://geoloqi.org/Mobile_App_Guidelines

The file LQConstants.h does not seem to exist in the project, so the app will not compile.

on the initial screens to give e-mail & password for log-in/token/OAuth, in addition to e-mail, password, Twitter OAuth & Facebook OAuth, there should be an OpenID initial sign-up/log-in choice. this should actually apply to all mobile clients for geoloqi (if such a section existed)(which it doesn't).

The Settings tab should be moved to the iPhone system settings. Items in the settings screen:

• OAuth status with "log out" button
• Username
• Remote Server address field
• Significant Updates option with note explaining what will happen

Hi-res (for iPhone 4) versions of the app icon and launch screen have been added, but not the tab bar icons. It appears Glyphish (where the icons came from) doesn't provide hi-res versions, but they do provide a vector PDF of all the icons which could be used to make our own.

A slider needs to be added to Controls for a minimum accuracy value. See http://dev.geoloqi.com/Mobile_Device_Control_Panel

Slider mappings have been put in SliderMappings.plist but currently aren't used. They should be loaded and used as mappings from the slider position to the actual filter values.

Things to consider:

• Which value should be stored in the user defaults, the slider position (index) or the actual mapped value? Probably the latter, since if the index is stored and the mappings change, it'd get screwed up.

When debugging the server, it would be helpful to be able to force an update to be sent from the phone. Since there isn't a way to force the phone to update its location, the button could at least re-send the last known location.