Retrospective: 25/10/2019

[andremedeiros]

Retro

The good

Things that went well that we should keep doing

• Successful PN POC for Android, conclusive (?) research for both platforms
• Roman is back!!(+100!)
• Performance investigation was very reve,raling (+1)
• Team's initiative to solve issues (e.g. notifications)
• @Roman solving back up seed phrase notification display within 2h of being back:) (+1)
• Potential contract UI contributor onboarding soon
• Trail of bits audit seems very thorough, nothing terribly critical yet

The bad

Opportunities we have to improve

• not for all new screens and elements accessibility-ids were added
  • [ ] Andre: follow up on a potential linter
• Spotty standups - lack of specific issues make it hard to track (& measure efficiency), increase risk of working off-spec or off-focus. Occasionally missing standups.
  • [ ] Andre: check out Pedro's stand up tool / bot
• We are fairly far from good performance (receiving messages, chat)
• Lots of design tagging, but could use more in case of any deltas from Figma design
• Not a huge amount of progress against v1 backlog

The ugly

Things that went badly that we have to change

• Lead wasn't around as much as he should

Themes

Other things we should discuss

• Push Notification POC & conclusions (iOS: https://notes.status.im/vDbGDuz3QUuzaLF4UHHhwA)

[andremedeiros]

@rachelhamlin's notes on PNs:

iOS PNs: Poor man's solution - schedule a notification every hour or more...? Manipulate algorithm to increase Status score. It would say "hey open Status" once an hour. Other alternative: user might be incentivized to run desktop or a node that Oskar is talking about. Enter chatkey on this node or desktop & it would send notifications to iOS. Andre: Not 100% sure you can just send notifications to the device, you may have to have a certificate. I'm 99% confident that this is not a thing on iOS. We could still implement background refresh in case people do use it enough. But if you use the app this much, you wouldn't need PNs anyway.