Wikimedia Apps/Team/iOS/Weekly Planning/2016-01-12

01/12

Action items:

• Add RTL tickets to Needs Estimation (https://phabricator.wikimedia.org/T116989) [JOSH]
• Create a task, "As a product manager I want to track how people are using the app so we can deliver relevant value" [JOSH]
  • Gotta find the schemas first
    • https://meta.wikimedia.org/wiki/Special:PrefixIndex/Schema:MobileWikiApp
    • https://meta.wikimedia.org/w/index.php?title=Special%3APrefixIndex&prefix=MobileWikiApp&namespace=470
• Josh and Nirzar to sync, talk about how Sherah can help with Navigation prototyping [JOSH/NZR/SHERAH]
• Create a ticket to implement the W ("Option 1") [JOSH]
• Spike task to investigate pageviews API, tech, etc for Trending [JOSH]
  • Brian to bring up in Scrum of Scrums, talk to Dan Andreescu [BRIAN]
• Research spike: Talk to Tomas about Apple Maps tiles [JOSH]
• Task for design to do a basic design of nearby with no maps [JOSH]
• We need a new design mockup for Delete All and Saved and History [NZR]
• Create a ticket for when the user has been denied permissions, what the consequences are, and how to re-enable [JOSH]
• Team to review https://phabricator.wikimedia.org/T109129 and raise any issues ahead of estimation [TEAM]
• Make a ticket for refreshing feed [JOSH]
• Find a ticket for, and if none, make a ticket for Footer on "Featured article" feed item for "Past featured articles" - uses "saved pages" style list with title being date [MONTE]

Agenda:

• Josh’s focus this week: get more user feedback, more people into the beta
• Goal: discuss status of voted on "production" items. Phab status, next step owner, scope/clarity.
• IRL Review
  • Photos: https://drive.google.com/open?id=0B-R9R4fm4jIiTVYzRXJabGZ6TDg
    • EXTRA LARGE
      • RTL
        • RTL tickets already exists, need sense of time from Monte on the ticket he has already filed. Epic ticket “as a right to left language user” and there are 5 or 6 blocking tickets.
          • Monte did an audit about the issues, but doesn't feel he needs to own it. Any of us can take the sub tasks.
            • Josh: Let's estimate them during estimation meeting tomorrow.
            • Epic: https://phabricator.wikimedia.org/T116989
    • LARGE
      • Analytics
        • Analytics is blocked on auditing existing schemas
          • Need a link to where those schemas are, blocked-on-Josh, Josh to write up flow
            • Then we need a ticket to implement what Josh requested
              • This _might_ be the comprehensive list: https://meta.wikimedia.org/wiki/Special:PrefixIndex/Schema:, see all "MobileWikiApp" schemas. Should also look at iOS app code. See also: https://www.mediawiki.org/wiki/Extension:EventLogging/Guide
      • Navigation
        • We need to decide what we are going to protoype, but need Nirzar to help make decision (is he at this meeting today?).
          • What is our actual final list? It seems to have changed since the IRL meeting.
            • We originally had 3
              • Narrowed based on Nirzar mocks to 2 main options:
                • 1 - Use the W menu to pop to root
                  • https://drive.google.com/a/wikimedia.org/folderview?id=0B-R9R4fm4jIiTVYzRXJabGZ6TDg&usp=drive_web#
                • 2 - Move the back and forth to the toolbar with either:
                  • < Back button
                    • https://drive.google.com/a/wikimedia.org/folderview?id=0B-R9R4fm4jIiTVYzRXJabGZ6TDg&usp=drive_web#
                  • Down button and or swipe to close
                    • (Nirzar mockup)
                      • Josh and Nirzar to sync, talk about how Sherah can help
                      • Ideally we implement the prototypes but right now we have limited bandwidth and would rather look into actual current user feedback than test something we only might need to fix. However, we need to get the ball rolling with regards to prototyping if we want to do any.
    • MEDIUM
      • Settings menu
        • Is in Needs Design, should be good to move through flow
      • Trending items - LET'S DO THIS!
        • Spike on technical concerns
          • API doc https://wikimedia.org/api/rest_v1/?doc#!/Pageviews_data/get_metrics_pageviews_per_article_project_access_agent_article_granularity_start_end
            • supports date ranges, is per-site
            • flagged as "Experimental" (but iOS app is also "experimental"—DO IT LIVE)
          • Talk to ABase & Dan Andreescu
            • Top trending item appears on feed - has "Top 100 trending articles" footer which loads "saved pages" style full list
              • The most popular pages tend to be the "same" and things like main pages - so we may want to scrub those things.
      • WP0
        • Audit existing implementation
          • ticket is in Design Doing
            • Map support for nearby
              • we could Implement Nearby as a tab without a map, just a list view (see: SMALL). There we need a design
              • The map thing hangs on Josh determining if we can use Apple Maps.
                • If it’s easy, no brouhaha, then we can do it.
                  • We need a research task for Josh to look into Apple Maps tiles
                    • more of a political thing: is it a bad idea to use Apple Maps when Mapbox is already deployed and in use
                      • caveat: we're guaranteed to have Apple Maps installed, unlike Android
                    • The other task is for design to do a basic design of nearby with no maps.
    • SMALL
      • Delete All Saved and History (and elsewhere!)
        • we have a design but it's not quite right, so we need a new design mockup.
          • Talk about existing ticket: https://phabricator.wikimedia.org/T115136
      • Hide feed items
        • should be ready for dev (is the mock acceptable for moving forward?): https://phabricator.wikimedia.org/T109129
          • Tech notes:
            • BG: Need to handle "persistent" deletion (i.e. rebuilding the feed shoudn't cause the section to re-appear)
              • BG: Or, we flag history item as "blacklisted"
      • Removing Singletons from the Feed
        • Let’s talk with group as part of planning agenda, scope out, before making ticket.
      • Feed Refreshing
        • Josh to find out if there is a mock for that. (Did not find a ticket)
          • Is there a research task?
          • Tech notes:
            • BG: Easiest, low-hanging fruit: add pull to refresh (or other control) that forces a total reload & scrolls to top.
            • BG: Next step: preserve scroll position after pull-to-refresh by prepending new items instead of rebuilding (twitter-like behavior). Has subtasks for non-functional requirements:
              • redo feed "building" process to instead only prepend new items
              • preserve existing section data in memory (and potentially to disk as another follow-on)
      • Footer on "Random" feed item for "More random items"
        • when tapped loads "saved pages" style list of random items
        • "infinite scroll" - when you scroll to bottom of list another chunck of random items is requested
        • request chunks of 25 items - only keep best 15 or so - "best" being articles with images and long-ish extracts
      • Footer on "Featured article" feed item for "Past featured articles" - uses "saved pages" style list with title being date
      • Nearby Tab (no maps)
        • we could Implement Nearby as a tab without a map, just a list view
      • Cell Data
        • need a spike, should be a ticket already for this
        • Brian's baby, he should pursue if he has spare time.
      • Prompt user to re-enable Location Services if denied