[p2pu-dev] problems with mobile UX on new.p2pu.org
Pippa Buchanan
Pippa.Buchanan at gmail.com
Sun May 29 15:36:04 UTC 2011
Speaking of APIs - Hemanth is developing a course on APIs and wants to work
on specifying one as part of their more advanced goals. I've mentioned that
P2PU need an API - perhaps this is a great way to get Webcraft participants
involved?
http://new.p2pu.org/en/groups/paws-on-web-apis/
P*
On 28 May 2011 06:31, John Britton <public at johndbritton.com> wrote:
> YES, API.
>
> I think minor tweaks to help mobile work better make sense, but would
> definitely head toward an API before building a mobile version of the site.
> An API would make it easier for us to develop the mobile version and make it
> possible for others to build cool stuff.
> --
> contact info:
> http://www.johndbritton.com
> @johndbritton - http://twitter.com/johndbritton
>
>
> On Fri, May 27, 2011 at 1:03 PM, Jessy Kate Schingler <jessy at jessykate.com
> > wrote:
>
>> another way to look at this is as a bit of a chicken and egg thing. if
>> it's painful to participate in the site from a mobile device, no wonder it's
>> only 5% of our traffic :).
>>
>> i generally agree with you that this isn't an immediate priority since we
>> have a lot of priorities! i also think the nature of most courses isn't such
>> that there's likely to be a huge mobile-device-participation contingent...
>>
>> although, it does make me wonder what that would look like, and if there's
>> some new opportunities there. for example, courses designed around game play
>> with very simple UI components to indicate task completion, or to correlate
>> to physical actions like arrival at a location or disvovery of an item
>> (imagining open street maps courses or civics courses).
>>
>> if anything i think this is equally an argument for an API for the site
>> (as you brought up the other day), as it is a mobile interface.
>>
>>
>> Jessy
>> --
>> http://jessykate.com
>>
>>
>>
>> On Fri, May 27, 2011 at 11:50 AM, John Britton <public at johndbritton.com>wrote:
>>
>>> +1 for a mobile version in the future, Maybe using JQuery Mobile.
>>>
>>> Honestly, it's not a priority right now. Mobile accounts for under 5% of
>>> our traffic (according to google analytics)
>>> --
>>> contact info:
>>> http://www.johndbritton.com
>>> @johndbritton - http://twitter.com/johndbritton
>>>
>>>
>>>
>>> On Fri, May 27, 2011 at 11:21 AM, zuzel.vp <zuzel.vp at gmail.com> wrote:
>>>
>>>> The wizzywig view of the editor does not opens the keyboard of the
>>>> nexus. Only the html view works ok. -- I think that was the issue with
>>>> "real textbox, not scripty one you got".
>>>>
>>>> --
>>>> Thanks,
>>>> Zuzel
>>>>
>>>> 2011/5/27 João Antonio de Menezes Neto <tonyhomes at gmail.com>:
>>>> > an ideal scenario would be a mobile version instead of a mobile
>>>> adapted
>>>> > theme, but it implies double development...
>>>> >
>>>> > 2011/5/27 Jessy Kate Schingler <jessy at jessykate.com>
>>>> >>
>>>> >> On both my android and ipad there is no "mobile" theming, so its just
>>>> the
>>>> >> same as the regular site. I don't find it *terrible*, but it
>>>> certainly could
>>>> >> be better for navigation and faster with a proper mobile style.
>>>> >>
>>>> >> --sent from my mobile
>>>> >>
>>>> >> On May 27, 2011 8:57 AM, "Philipp Schmidt" <philipp at p2pu.org> wrote:
>>>> >> > On 27 May 2011 14:53, Jessica Ledbetter <
>>>> jessica at jessicaledbetter.com>
>>>> >> > wrote:
>>>> >> >> It looked alright last I checked on the iPad but I haven't pulled
>>>> it up
>>>> >> >> on
>>>> >> >> the iPhone.
>>>> >> >> We can do a mobile css (though actually there might be one
>>>> already) or
>>>> >> >> a
>>>> >> >> real mobile site probably.
>>>> >> >> But yes, definitely should work well on mobile.
>>>> >> >
>>>> >> > I am hoping this is something we can ask Mozilla to look at - since
>>>> it
>>>> >> > would affect drumbeat.org and their other sites as well.
>>>> >> >
>>>> >> > -- P
>>>> >> > _______________________________________________
>>>> >> > p2pu-dev mailing list
>>>> >> > p2pu-dev at lists.p2pu.org
>>>> >> > http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>> >>
>>>> >> _______________________________________________
>>>> >> p2pu-dev mailing list
>>>> >> p2pu-dev at lists.p2pu.org
>>>> >> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>> >>
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > p2pu-dev mailing list
>>>> > p2pu-dev at lists.p2pu.org
>>>> > http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>> >
>>>> >
>>>> _______________________________________________
>>>> p2pu-dev mailing list
>>>> p2pu-dev at lists.p2pu.org
>>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> p2pu-dev mailing list
>>> p2pu-dev at lists.p2pu.org
>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>
>>>
>>
>> _______________________________________________
>> p2pu-dev mailing list
>> p2pu-dev at lists.p2pu.org
>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>
>>
>
> _______________________________________________
> p2pu-dev mailing list
> p2pu-dev at lists.p2pu.org
> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20110529/61982d1c/attachment.html>
More information about the p2pu-dev
mailing list