Back to Mobile Design, back to Mobile Feedback

List issues below

V3.2

V3.2RC1

iPod Touch 2nd generation running iOS 4.2.1.

Scrolling bugs and layout issues are fixed. (However there's a minor issue with expandable templates like those in the External links section of U2; the "v", "t" and "e" links are displayed in a bullet list vertically. The same problem exists on the mobile site.)
The Back-button in lower left doesn't work. It usually sends me to the top of the current article, not to the previous article. Occasionally it works correctly.
Fixed14.96.230.194 23:14, 11 June 2012 (UTC)[reply]
Problems 2, 3, 6 from my review of V3.2Beta2 below are still present.
Can't reproduce 2. Working on fixing 3 and 6. 14.96.230.194 23:14, 11 June 2012 (UTC)[reply]
Saving a page for offline use usually works, and saved pages can be accessed offline. However, the app reproducibly crashes if I try to save the page U2, maybe memory issue?
Yes, possibly memory issue. Works fine for me though :( 14.96.230.194 23:14, 11 June 2012 (UTC)[reply]
The history of visited pages often shows an entry multiple times in a row, even though the page was visited only once. (This is clearly the cause of problem 2.)
When reading an article and clicking on an external link, I'm sent to Safari as expected. When I then close Safari and re-open the Wikipedia app, I expect to still see the same article, but instead I get the main page again.
Lack of multi tasking in iOS? I know this works fine-ish on 5.x... 14.96.230.194 23:14, 11 June 2012 (UTC)[reply]
After touching a link by mistake, I expected the X in the upper right (next to the search field) to interrupt loading and go back to the old page, but apparently it does nothing.
Ouch. On it! 14.96.230.194 23:14, 11 June 2012 (UTC)[reply]

AxelBoldt (talk) 23:32, 24 May 2012 (UTC)[reply]

V3.2Beta2

iPod Touch 2nd generation running iOS 4.2.1.

Scrolling is much smoother, but the bug listed below is still present: Go to the Wikipedia article on "Baden-Baden", open the section "Sights" and scroll down. After one or two screenfuls, you can't scroll down any further, though you can scroll back up. It happens in many articles, whenever a section is too long.
If I have no network connection, bring up a previously stored page and click on a link there, I get a blank page, no error message.
If I have no network connection and pick "nearby pages", I get a blank map, no error message.
When tapping on a reference footnote, the reference box opens. If I click on any external link in that box, I'm sent to a new window with the Safari browser, but scrolling is impossible in the new window.
When tapping on a Wikipedia-internal link contained in a reference box, I expect to remain in the app but instead I'm also kicked out of the app and sent to Safari.
When searching for "Miller" I get 10 results; tapping on "show more results" gives another 10. The previous results are lost and cannot be recovered; it would be better if the new ones would be appended to the old ones. Worse: if I click on "show more results" again, I won't get any more, even though there are many more than 20 hits for "Miller" in Wikipedia.
Go to "U2", open section "External links": layout is really poor.

AxelBoldt (talk) 22:24, 8 May 2012 (UTC)[reply]

V3.2Beta1

This is on an iPod Touch 2nd generation running iOS 4.2.1.

(Showstopper) After searching it is impossible to scroll through the list of results; as soon as you touch the result list you're sent to the first article you touched. The same happens in the history of visited pages.
- Fixed yesterday :) Yuvipanda (talk) 14:08, 4 May 2012 (UTC)[reply]
(Showstopper) Scrolling within an article is significantly worse than in v3.1.1rc2. It seems the display is updated only when you stop moving the finger, never before. So you never get the impression of actually "moving" the page. There is also a definite bug in the scrolling code: Go to the Wikipedia article on "Baden-Baden", open the section "Sights" and scroll down. After one or two screenfuls, you can't scroll down any further, though you can scroll back up. It works fine in landscape mode. This is reproducible for me.
- Sigh. My 4.x test device is still on the way, will debug when it gets here. Yuvipanda (talk) 14:08, 4 May 2012 (UTC)[reply]
When searching, there are greyed out "Previous" and "Next" buttons above the keyboard whose purpose remains obscure.
- Those are iOS's ways of moving to next and previous input items in a form. I'm unsure of a way to remove them from js. Will file a bug Yuvipanda (talk) 14:08, 4 May 2012 (UTC)[reply]
When clicking on a reference footnote, the reference appears in a box, which is nice. When clicking on a Wikipedia link in that box, I'm kicked out of the app and sent to the mobile site in Safari.
- Removing the ^ Yuvipanda (talk) 14:08, 4 May 2012 (UTC)[reply]
(Wishlist) After having searched and obtained a result list, the search box still contains the term you searched for, which is fine. If you then want to search for a different term, there should be a quick way to clear out the search box (grey circled X at right of search box seems to be a common convention, see Safari search box).
- We had this functionality before, disabled because of focus issue on Android. Works fine on iOS, will re-enable Yuvipanda (talk) 14:08, 4 May 2012 (UTC)[reply]
(Wishlist) I liked the option to close an expanded section once you have read through it, so that you can pick another section to open next. Maybe a tiny TOC icon at the end of every section, that would bring you back to the table of contents with all sections closed?
(Wishlist) In the share menu there should be an option to email a link to the article.
- There's a bug for it. Will add in a future version :) Yuvipanda (talk) 14:08, 4 May 2012 (UTC)[reply]
(Wishlist) As mentioned a couple times below, in the Nearby Search view the +/- zoom buttons obscure the popup texts.
- https://bugzilla.wikimedia.org/show_bug.cgi?id=36004 Yuvipanda (talk) 14:08, 4 May 2012 (UTC)[reply]

AxelBoldt (talk) 19:20, 3 May 2012 (UTC)[reply]

V3.1

v3.1.2rc1

Nearby pages

In "Nearby pages", the zoom buttons always obscures the title of the article making it difficult to read. Either the text bubble should appear over the zoom buttons or the zoom buttons should be moved to the bottom of the page.
In "Nearby pages", you can't move the map if your finger is on an article.

Display anomalies

Infobox captions ('.infobox caption' in the CSS) don't show up as bold even though they are defined as bold. They show up correctly in the regular mobile view.
The inline coord template ({{Coord}}) displays with extra spacing after it, but doesn't in the regular mobile view.

Confusing UI

I can't figure out what the "Jump back a section" link is supposed to be for. It seems to just hide the section your reading, in which case, wouldn't it make more sense to call it "Hide section".

Kaldari (talk) 03:04, 14 April 2012 (UTC)[reply]

v3.1.1rc2

(This is on an ipod touch 2nd generation running iOS 4.2.1)

Startup of the app is slow: initially the complete interface appears with forward/backward button in white, then it loads something with spinning circle in the center, then the bottom row is blanked out, then reappears with arrows greyed out, then it loads some more with spinning circle in search box.

The +/- zoom buttons partly obscure the text bubbles in nearby pages view.

At the bottom of the search results there's a line "show more results", but you can't select it because if you scroll down there, it magnetically scrolls back up again.

Permanently shown search box takes up too much space, especially in landscape mode.

When scrolling in the search results list, the last result touched is underlined. That's not helpful: there should be some visual feedback when tapped on, not during scrolling.

The keyboard should disappear as soon as the user starts to scroll in the search results. Otherwise search in landscape mode is unusable.

When reading an article and opening a section, there's a "jump back a section" link at the end of the section. That link however jumps to the bottom of the article, not to the previous section.

When tapping on a section header to open the section, there should be some visual feedback (invert the button), because sometimes it takes a while for the section to open.

This should be addressed in the new section style that just appeared on the mobile site beta. This will carry over into the apps soon.--Phil Chang, Mobile Product Manager (talk) 17:42, 13 April 2012 (UTC)[reply]

If I'm offline and go to a stored page, then click on a link, I get the message "page not available in offline mode", which is fine. If I then tap on the back arrow, I should be sent back to the stored page, but instead I get another "page not available in offline mode" which is incorrect.

Feature suggestion: add an option to prevent downloading of images. This is important for slow connections. You could replace every image with a box of equal size containing a link, so that the user can read the caption and decide on a case by case basis whether they want to download that image.

This one has existed in the backend for a while, but is not yet exposed in the UI.--Phil Chang, Mobile Product Manager (talk) 17:39, 13 April 2012 (UTC)[reply]

Feature suggestion: allow to search for articles near a given address/location, e.g. when planning a trip or when location service is not available.

AxelBoldt (talk) 02:06, 16 April 2012 (UTC)[reply]

Back goes to actual state of the last page as it was left - same viewing position, same sections open (via email)

Go button on the keyboard should be removed (via email by Axel)

Strange "index.html" message when clearing saved pages (via email by Axel)

"About this app" from below (Jarry)

Share vie email from below (Jarry)

--Phil Chang, Mobile Product Manager (talk) 18:15, 10 April 2012 (UTC)[reply]

Jarry1250 (iOS 5.0.1)

General/other:

If I'm being nitpicky, I'd have a few more pixels between Show/Hide (section) and the section name, and I would also make the two buttons the same width, or at least pad so that the heading doesn't jump to the left/right when you toggle.
"Jump back a section" seems to simply collapse the section preceding it... not sure what the use case is? Perhaps it's just a case of changing the label to something more informative - there's actually no "jumping" involved? Or maybe change the functionality so it opens the preceding section and well as collapsing the current one. Or at least scrolls so you can see the collapsed header of the previous section!

Settings:

"About Us" is an odd label - why not simply "About"?
- "About this app" could be a more suitable name --Phil Chang, Mobile Product Manager (talk) 18:15, 10 April 2012 (UTC)[reply]
Per my Android comment, if you go onto (say) settings, you can still use Share, which seems odd because you'd have thought the article context wasn't still in play (these are global settings).
I completely misunderstood what the "Language" option did in the settings - it starts you out on a different Wikipedia, whereas I thought it would translate the interface (which it didn't).

Share menu:

Why is Share via Email not available on iDevices? :/
What's the difference between "Save page" and "Save to Read It Later" (except that the latter requires a registration"? Are Twitter, Read It Later and Facebook hardcoded options, or is it locale sensitive?
Maybe it's just me being dopey, but I pressed "Share to Facebook", theen it prompted me to log in, so I logged in, then it did nothing... I had to press the button again to prompt it to actually request a wall post. And even then, the Main Page is not given a title (on the FB post, or when you Save page) :(

This has been partially fixed. Main page titling laters :) Yuvipanda (talk) 23:27, 26 March 2012 (UTC)[reply]

Other menu:

Probably obvious, but I wouldn't have expected to find "nearby" on this menu.
Unlike on Android, my iPod touch failed to get my GPS data first time on Nearby. This is because it didn't request GPS clearance from my device; when I manually gave it the perms "Nearby" started working (flawlessly, although it could probably start more zoomed out when there isn't much around).
It would be neat if, when you pressed the wrong Nearby link accidentally (or you didn't realise they were links - more visual indication, e.g. a "See more" teaser link, perhaps?) and then you pressed the back button, you went back to Nearby, rather than the last article. Ditto going forward to Nearby if you've gone back from it.
Sometimes / often when I revisited Nearby, it wasn't broken; it started really zoomed out, for example, and then continued to glitch out when I tried to zoom in. One time it simply didn't show the pointers. More investigation needed.
History appears to have a significant visual glitch on my device, with some items (not every other one, but similar) not showing, and then scrolling causing some to appear and others to disappear.
(update:) Ohhh, the X in history clears the list. Wouldn't have guessed, sorry.

Thus it seems "Nearby" and "History" have significant glitches. Sorry! Jarry1250 (talk) 21:36, 23 March 2012 (UTC)[reply]

Nice to see the reference scrolling bug fixed and the images centered, great work!
The thing that still bugs me most is the hashlinks bug and the the absence of the "Redirected from" notice
The Share menu items are not localized
I find the "Jump back a section" link confusing and useless, too
On history menu, there is a clear glitch left to the delete button (a small white pixels vertical line)
The history deletion confirm dialog has title and cancel button not localized
When I do that: Page 1 -> Page 2 -> Nearby -> Back button, I find myself in Page 1 instead of Page 2
And finally, hey Yuvi, your name is cited two times in contributors under the About tab ;)
(added) Tapping Go on the keyboard when searching should work like the site Go button or bring you to the first page in the search results list

--FiloSottile (talk) 07:50, 24 March 2012 (UTC)[reply]

v3.1Beta3

Notes from Reedy: Reference reveal (scroll down to references) and general hashlinks do not seem to work.

Fixed

v3.1Beta2

Past discussions and solved issues archived here: Wikimedia Mobile engineering/imported/Mobile projects/WikipediaMobileiOSFeedback/ArchiveV3.1Beta2

When I'm in the Nearby screen and I tap on the bubble to go to an article, then go back to the Nearby screen (via the menu on the bottom bar) it sends me back to the default location instead of returning to where I previously was on the map. If I'm exploring an area I'm likely to tap an article, go back to the map, tap a different article, go back to the map, etc. It is painful to have to re-navigate to the spot (especially if I am, for example, looking around the Boston Commons for my hypothetical trip next week). Bhartshorne (talk) 00:47, 8 March 2012 (UTC)[reply]

On it. Yuvipanda (talk) 21:44, 9 March 2012 (UTC)[reply]

Bugzilla:35236 - Potentially bumping to 1.2 (along with other map work) Yuvipanda (talk) 01:17, 15 March 2012 (UTC)[reply]

On the Search bar, when you first open the app the status circle on the right hand side is spinning even though I didn't load anything. When it loaded the Main Page, the circle keeps on spinning - it's endless! The Helpful One 00:48, 8 March 2012 (UTC)[reply]

Crashed twice so far on my phone:

The Helpful One 00:54, 8 March 2012 (UTC)[reply]

Will check it out on 5.1 asap!

I'm on a G3 iPhone. Here are the problems I found in order of severity:

After expanding a section of an article, the app seems to become confused about where the bottom of the page is and if I scroll beyond a certain point in the article it snaps back to the false "end" point (usually a random spot in the middle of the article). I imagine this is because the app thinks the page is still the same height as it was before the content was expanded. This makes the app unusable for reading articles.
The page scrolling is very jumpy. This makes it pretty useless for reading long articles as you can't keep track of what line you were on when you scroll. This problem would actually keep me from using this app. Text scrolling is completely smooth in all my other apps and when reading Wikipedia in Mobile Safari (or the old Wikipedia Mobile app).
After you choose a page to go to from the search results, it doesn't automatically dismiss the keyboard.
The text of the license disclaimer at the bottom is in the exact same font and style as the article text, so it looks like it's part of the article.
There's a broken image after "Tiles Courtesy of MapQuest" in the Nearby interface.

Kaldari (talk) 23:44, 8 March 2012 (UTC)[reply]

last two have been fixed Yuvipanda (talk) 00:50, 16 March 2012 (UTC)[reply]

iPad 2 5.0.1 here. It.wiki mainly. Most important problem encountered is how redirects are handled: there is no "redirected from" banner and section redirects are not working, the page gets opened but the relevant section is not showed neither scrolled. For some pages this is really confusing. --FiloSottile (talk) 16:17, 12 March 2012 (UTC)[reply]

Not sure how to handle this, needs some MF work (?). Will check with jdlrobinson

Also, since thumbed images and templates get stretched to 100% width it would be nice to get also the images centered. Maybe with templates it may break layout, but it should not be difficult with |thumb| images. It really "feels wrong" to see the image aligned on the left and the description text centered. --FiloSottile (talk) 16:22, 12 March 2012 (UTC)[reply]

Will poke jdlrobinson on this.

Tapping on the note number [n] the Notes section gets shown (unhidden) but the page doesn't scroll and the note doesn't get highlighted. Likewise, the small ^ to go back to reading doesn't work. --FiloSottile (talk)

V3.1Beta1

Fixed issues are archived Here

There are two back buttons in the About Us screen and they behave differently. The top back button takes you back to the settings but the bottom back button takes you back to the article you were visiting. Bhartshorne (talk) 22:27, 1 March 2012 (UTC)[reply]

bugzilla:34908
- Was fixed, but then Jon convinced me that the best idea is to hide the nav bar when there is a overlay being shown. On it.

V2.2.2

Open Issues

if you search for a page nearby, then enter a new search in the search box at the top of the page and navigate to that page, an entry for the searched-for page goes into the history but choosing that page from the history screen takes you to the original 'nearby' page. Example: search nearby and choose the 'wikimedia foundation' page (because I'm testing from the office). On the WMF page, enter 'Thoreau' in the search box, go to the page, follow a link for 'Civil Disobedience'. Click the 'nearby' button to go back to the map page, then click the 'done' button to go back to the main screen. Load the history (by clicking on the clock icon) and tap the entry for 'Thoreau' or 'Civil Disobedience'. Observe you land on the WMF page, not the intended page. Bhartshorne 23:07, 6 January 2012 (UTC)[reply]
- Should be fixed in the new PhoneGap build Tfinc (talk) 22:54, 1 March 2012 (UTC)[reply]

on a slow connection, the 'loading' splash screen stays on the page until images are finished loading, even if you the text has fully loaded. When you don't need the images, it's annoying to have to wait for them before looking at any of the content. The app should allow scrolling even while it is still loading so that the user can read content before all the images have downloaded. Bhartshorne 23:07, 6 January 2012 (UTC)[reply]
- This should be fixed in our new PhoneGap build Tfinc (talk) 22:50, 1 March 2012 (UTC)[reply]

After looking for pages in the 'nearby' section, if you leave the app then return to the app, you are still buried in the 'nearby' interface and must tap twice back through the map. When re-entering the app for a new browsing session, it doesn't make sense to still be buried in the nearby section. Exiting the app and re-entering should load up the previously visible article in the main interface, not the nearby interface. Bhartshorne 23:12, 6 January 2012 (UTC)[reply]

We've heard mixed responses to this. I personally hate getting back to any app and finding that its changed the last screen that I was on. I expect it to resume right where I left off. Tfinc (talk) 22:50, 1 March 2012 (UTC)[reply]

This bug is now moot, actually. Previously, pages that you had found through the map were different from pages you found other ways. Now it appears that they are the same, so you're right, it should re-open to the page you were on when you left. It wasn't the page I wanted to change but the app's understanding of where you were in your workflow. The workflow's now the same either way, so it no longer matters. :) Bhartshorne (talk) 22:58, 1 March 2012 (UTC)[reply]

Formatting of the reference section into two columns is inappropriate for the size of the iPhone screen. The result is 1-3 words per line and excessive wasted space between the columns. On pages that use the template {{Reflist|2}}, it should be suppressed back down to one column. Example: w:en:Cepheid variable Bhartshorne 23:35, 6 January 2012 (UTC)[reply]
- bugzilla:34787

feature request There's no 'open in safari' link in the app. Most iOS apps that show you web pages in some way (eg facebook, byline, echofon) have an icon with options such as 'open in safari', 'email this page', 'copy link location', 'read later' (with something like instapaper), etc. Bhartshorne 00:02, 7 January 2012 (UTC)[reply]
- bugzilla:31475

on app startup, the first thing it does is load the Featured Article. 99% of the time I start the app, I am interested in searching for a specific page, but must sit through waiting for the FA to lead before I can perform my search (all interaction is disabled while a page is loading). This is annoying (and actually the primary reason why I started using a non-WMF wiki reader). Please either load the cached version of the previously read page or a splash screen instead of loading a fresh article. Note that this only happens when the app is freshly started, not when it is 'resumed' - if iOS backgrounded the app it will load to the previously viewed page. Bhartshorne 19:10, 11 January 2012 (UTC)[reply]
- bugzilla:31924