​​About MP release-Flexibility as a hidden feature
​​
  • ​​Topic: How we manage to ship the MP while assets/dependencies may come at the last minute
  • ​​Highlights: 
  • ​​
  • ​​Assets coming late are what cause issues
  • ​​Put everything in backend, make it independent from release
  • ​​Configure from CMS
  • ​​In MP, pull configuration of assets/layout from the backend
  • ​​Helps propagate/manage changes from staging to prod
  • ​​Same as mobile admin
  • ​​Sh*t happens → client can’t get it in time → process to get final asset is long and convoluted
  • ​​Tried many other ways:
  • ​​Point at the risk
  • ​​Point at the cost (overtime)
  • ​​Schedule and enforce timeline
  • ​​None of it work → we’re slave to the HQ
  • ​​Consequences of late assets → potential bugs, delayed release date, overtime
  • ​​Creatives at the core of the problem → not great at managing schedules and change opinion often + opinionated
  • ​​Until now no hard consequences for them (they don’t see the overtime)
  • ​​+7 hours behind
  • ​​Opening on features
  • ​​Business angle: Launching your WeChat mini-program the smart way
  • ​​Resources:
  • ​​Plan:
  • ​​Intro: we’ve done MP for a lot of folks, at speed with large MNC. Can be challenging; assets come late, things change half way, … 
  • ​​Problem: How do we make sure things are working
  • ​​Challenges:
  • ​​Large scale, multiple owners, moving targets
  • ​​Review process (Similar to iOS/Android (SBUX)
  • ​​Change in strategy
  • ​​Creatives
  • ​​Bugs in prod
  • ​​6 weeks to release
  • ​​Cost & Risk (opportunity cost)
  • ​​We’re all about getting shit done
  • ​​Timezones
  1. ​​Application size can not be over 10MB (this used to be 3MB before, but has been increased a few months ago)
  • ​​Best practices
  • ​​CI/CD (post) + Automation
  • ​​Complex stuff in backend
  • ​​Planning (demo spreadsheet?)
  • ​​CMS → expand on that → Who does what
  • ​​Coordinate with your marketing (early)
  • ​​UAT (with end users/stakeholders/clients)
  • ​​Test analytics too w/ data strategy
  • ​​Monitoring + Logging and that includes front-end (sentry)
  • ​​Having tech team available on launch (~1 hour)