Wikimedia Apps/Wikipedia/iOS/Feedback

List issues below

= V3.1 =

v3.1Beta2
The gray 'x' to close the popup bubbles in the Nearby screen take 2-4 tries to actually hit. Please make the target area to activate the x larger. Bhartshorne (talk) 00:42, 8 March 2012 (UTC)\
 * Hmm, you can tap anywhere else on the map to close the bubble. I'd suppose getting rid of the (x) is the best idea.
 * to kill the X, hated it. If it wasn't there, I would tap on the map. --FiloSottile (talk) 19:32, 9 March 2012 (UTC)
 * The X has been killed. Yuvipanda (talk) 21:25, 9 March 2012 (UTC)

When I tap on a bubble in the Nearby screen to load the full article, the screen flashes to whatever article I was on previously momentarily then starts loading the new article. It's odd when I'm looking at nearby related articles to be looking at the popup for, say Chez Panisse and tap it, but flash up the article for the Cheese Board momentarily - it makes me think I missed the target (since they're nearby). The blank white screen that popped up before wasn't good either, but I think this might be worse. Can we just have a 'loading' screen or something instead of either the full blank or the previous article? Bhartshorne (talk) 00:47, 8 March 2012 (UTC)
 * Hmm, not sure what is the best way to go about this. Don't know if showing a modal dialog is a good idea. Let me poke our UX folks about this Yuvipanda (talk) 21:25, 9 March 2012 (UTC)

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)
 * On it. Yuvipanda (talk) 21:44, 9 March 2012 (UTC)

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)

Crashed twice so far on my phone:
 * 
 * 

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

I'm on a G3 iPhone. Here are the problems I found in order of severity: Kaldari (talk) 23:44, 8 March 2012 (UTC)
 * 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.

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)
 * 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.

On the Nearby screen, the attribution (Powered by Leaflet - Tiles courtesy of Mapquest yadda yadda) takes up too much screen real estate. Yes, we want to attribute the provider, but please make it go away or something and stop wasting precious map area Bhartshorne (talk) 22:46, 1 March 2012 (UTC)
 * 34910
 * Leaflet told us we can move their part off into the about section. Phil's talking to the Mapquest folks to see if we can move that too.

= 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)
 * Should be fixed in the new PhoneGap build Tfinc (talk) 22:54, 1 March 2012 (UTC)


 * 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)
 * This should be fixed in our new PhoneGap build Tfinc (talk) 22:50, 1 March 2012 (UTC)


 * 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)
 * 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)
 * 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)


 * 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 , it should be suppressed back down to one column.  Example: Cepheid variable Bhartshorne 23:35, 6 January 2012 (UTC)
 * 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)
 * 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)
 * 31924