As I said. I can see both sides of the argument. I'll say it again: ___Data.___
I can imagine some useful metrics might be as follows: For a given page that we decide to run an A/B test on... * Given a page has all sections expanded by default how many sections are closed * Given a page has all sections collapsed by default how many sections are opened * Given a page has all sections expanded when the reader leaves the page what is the furthest open section they view in the visible viewport area of the screen - calculate average * Given a page has all sections collapsed when the reader leaves the page what is the furthest open section that they reach - calculate average I would say we should be optimising for: * the lower amount of clicks (better experience for the user all round) * for the furthest down the page (measures engagement of article) In terms of results if the results highly favour one situation we should use that situation If the results show a 50/50 split / are inconclusive this suggests a preference/button would be the way to go. We may also want to record referrer as certain behaviours might be favoured when coming from a google search result over coming from a wikipedia mobile link/search result. If this sounds like a good starting point we can start developing a schema on the wiki? On Tue, Sep 17, 2013 at 12:49 PM, James Alexander <[email protected]> wrote: > [that said a 'collapse all' certainly helps my concerns, since I can just > click that] > > James Alexander > Legal and Community Advocacy > Wikimedia Foundation > (415) 839-6885 x6716 @jamesofur > > > On Tue, Sep 17, 2013 at 12:48 PM, James Alexander <[email protected]> > wrote: >> >> On Tue, Sep 17, 2013 at 12:38 PM, Steven Walling <[email protected]> >> wrote: >>> >>> >>>> I'm not sure I agree with Steven's assessment that this will make >>>> navigating between sections difficult - behaviour gets reverted - you close >>>> the section to see the next section. This is akin to flicking through a >>>> book >>>> and flicking to the next page (closing the section) if the heading at the >>>> top of the page doesn't interest you. It just means you don't see all the >>>> headings in one go which could be a good or bad thing. >> >> >> >> Right... but if you don't actually see the other sections you have to >> start closing them all to find out what is actually available. I know, at >> least in my case, that will likely mean I just navigate away (or switch to >> desktop view). In general I've found that what you 'see' at the start is >> very important. Honestly I'm surprised it's even a question.. I can see >> arguments for it being uncollapsed by default (find on page etc, even if I >> don't agree with them) but there is little doubt in my mind that it hurts >> the easy navigation. This is especially true without a table of contents >> (which the compressed sections basically acted as), in a book you don't just >> flick to the next page, you look at the TOC and know where to go. >> > > > _______________________________________________ > Mobile-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/mobile-l > _______________________________________________ Mobile-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mobile-l
