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

01/12

edit

Action items:

edit
  • 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]
  • 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:

edit
  • 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.
      • LARGE
      • MEDIUM
        • Settings menu
          • Is in Needs Design, should be good to move through flow
        • Trending items - LET'S DO THIS!
        • 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!)
        • 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