GoogleCodeExporter
``` What problem are you trying to solve / opportunity you're addressing? mobile users who hear about AFG don't have a great experience, e.g. when they get tweets about us. Describe the rough idea: Sniff the User-Agent to detect iphones then tune the output for them in the HTML/JS. Some eng options: 1. create a separate set of HTML templates for iphone. This is ideal, but requires staffing to maintain long-term-- could be owned by whoever owns the iphone app, i.e. in exchange for a link on iphone SERPs to "get the AFG iphone app." 2. make small/strategic tweeks to the HTML/JS, i.e. {% if iphone %} in the django templates. This is best if we don't have staffing to maintain separate pages. 3. use a variation of the gadget. The gadget is already tuned for for small screens, but it lacks many key features, including the viral/social ones. That said, we do have staffing to maintain the gadget, so perhaps we could extend the gadget... Does this require anything beyond writing code? no. In the 18 month timeframe, how much impact could this have (number of people impacted)? have you considered all the steps involved (e.g. approvals, user signups, etc.) and whether they would slow us or limit scale? Depending on who you believe, mobile is becoming a huge part of the user base. Can this be implemented in 3 months or less? yes-- depending on the option you pick, it could be a week or less. How does this impact users? better user experience for mobile, no change for desktop/laptop. How does this impact organizers? more volunteers. How does this leverage partners? n/a unless a partner maintains this. Does this bring up new legal/policy problems? no. ``` Original issue reported on code.google.com by `adam.sah` on 5 Jul 2009 at 5:41