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 :). <div><br></div><div>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... </div>
<div><br></div><div>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). </div>
<div><br></div><div>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. <div><div><br clear="all"><div><br></div><div>Jessy</div><div>--</div>
<div><a href="http://jessykate.com" target="_blank">http://jessykate.com</a></div><br>
<br><br><div class="gmail_quote">On Fri, May 27, 2011 at 11:50 AM, John Britton <span dir="ltr"><<a href="mailto:public@johndbritton.com">public@johndbritton.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
+1 for a mobile version in the future, Maybe using JQuery Mobile.<div><div><br></div><div>Honestly, it's not a priority right now. Mobile accounts for under 5% of our traffic (according to google analytics)</div><div>
--<font color="#888888"><br>
contact info:<br><a href="http://www.johndbritton.com" target="_blank">http://www.johndbritton.com</a><br>@johndbritton - <a href="http://twitter.com/johndbritton" target="_blank">http://twitter.com/johndbritton</a></font><div>
<div></div><div class="h5"><br>
<br><br><div class="gmail_quote">On Fri, May 27, 2011 at 11:21 AM, zuzel.vp <span dir="ltr"><<a href="mailto:zuzel.vp@gmail.com" target="_blank">zuzel.vp@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The wizzywig view of the editor does not opens the keyboard of the<br>
nexus. Only the html view works ok. -- I think that was the issue with<br>
<div>"real textbox, not scripty one you got".<br>
<br>
</div><font color="#888888">--<br>
Thanks,<br>
Zuzel<br>
<br>
2011/5/27 Joćo Antonio de Menezes Neto <<a href="mailto:tonyhomes@gmail.com" target="_blank">tonyhomes@gmail.com</a>>:<br>
</font><div><div></div><div>> an ideal scenario would be a mobile version instead of a mobile adapted<br>
> theme, but it implies double development...<br>
><br>
> 2011/5/27 Jessy Kate Schingler <<a href="mailto:jessy@jessykate.com" target="_blank">jessy@jessykate.com</a>><br>
>><br>
>> On both my android and ipad there is no "mobile" theming, so its just the<br>
>> same as the regular site. I don't find it *terrible*, but it certainly could<br>
>> be better for navigation and faster with a proper mobile style.<br>
>><br>
>> --sent from my mobile<br>
>><br>
>> On May 27, 2011 8:57 AM, "Philipp Schmidt" <<a href="mailto:philipp@p2pu.org" target="_blank">philipp@p2pu.org</a>> wrote:<br>
>> > On 27 May 2011 14:53, Jessica Ledbetter <<a href="mailto:jessica@jessicaledbetter.com" target="_blank">jessica@jessicaledbetter.com</a>><br>
>> > wrote:<br>
>> >> It looked alright last I checked on the iPad but I haven't pulled it up<br>
>> >> on<br>
>> >> the iPhone.<br>
>> >> We can do a mobile css (though actually there might be one already) or<br>
>> >> a<br>
>> >> real mobile site probably.<br>
>> >> But yes, definitely should work well on mobile.<br>
>> ><br>
>> > I am hoping this is something we can ask Mozilla to look at - since it<br>
>> > would affect <a href="http://drumbeat.org" target="_blank">drumbeat.org</a> and their other sites as well.<br>
>> ><br>
>> > -- P<br>
>> > _______________________________________________<br>
>> > p2pu-dev mailing list<br>
>> > <a href="mailto:p2pu-dev@lists.p2pu.org" target="_blank">p2pu-dev@lists.p2pu.org</a><br>
>> > <a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
>><br>
>> _______________________________________________<br>
>> p2pu-dev mailing list<br>
>> <a href="mailto:p2pu-dev@lists.p2pu.org" target="_blank">p2pu-dev@lists.p2pu.org</a><br>
>> <a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> p2pu-dev mailing list<br>
> <a href="mailto:p2pu-dev@lists.p2pu.org" target="_blank">p2pu-dev@lists.p2pu.org</a><br>
> <a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
><br>
><br>
_______________________________________________<br>
p2pu-dev mailing list<br>
<a href="mailto:p2pu-dev@lists.p2pu.org" target="_blank">p2pu-dev@lists.p2pu.org</a><br>
<a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
</div></div></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<br>
p2pu-dev mailing list<br>
<a href="mailto:p2pu-dev@lists.p2pu.org">p2pu-dev@lists.p2pu.org</a><br>
<a href="http://lists.p2pu.org/mailman/listinfo/p2pu-dev" target="_blank">http://lists.p2pu.org/mailman/listinfo/p2pu-dev</a><br>
<br></blockquote></div><br></div></div></div>