Skip to content

notes.md

Latest commit

 

History

History
162 lines (144 loc) · 4.96 KB

notes.md

File metadata and controls

162 lines (144 loc) · 4.96 KB

TODO:

PRIORITY

  • Show current games when nav back home
  • flex for past games on welome screen
  • minimum display time for shroud
    • quite glitchy now when the server is fast
    • write a par map2 and do the API call with a delay? <- blog
  • how to play
  • Write blog posts
    • overall design
      • inspiration
      • architecture
    • API
      • Attempt
      • tests
    • frontend
      • elm basics
      • CSS framework
    • infrastructure
      • lambda considerations
      • cloudformation
      • build (not yet cloudformed)
    • user testing (playing)
      • move trade-offs away from tech towards usability ` edge case / race condition from finish pitch change
      • UI simplifications - move away from physical card ideas
    • learnings
      • model as union type, not single object with optional bits

UI

  • consider skipping "loading backend" message
  • screen to show full standings (with words/role)
  • Say on spectating page what the currently active role is?
    • and who has that role?
  • Error screen header margin (and generally fix that screen's display)
  • Stanley pictures on loading screens

GENERAL

  • track "product" to help buyer choose and for standings
  • change screen name to player name in API so error messages match UI
  • Show joined players on CreatorWaiting screen
  • better asset versioning (cache headers) so updates manifest?
  • error handling (minimise usage of generic error view)
  • UI tests that ensure user journey
  • manage game screen for creator
    • manage buyer
    • kick players
    • allow player to join after start (share a join link from in game / creator waiting)
  • use flags for api endpoint config
  • disallow duplicate screen names

BUILD / OVERHEAD

  • cloudformation for build pipeline
  • refactor backend into sub-project

LONG TERM

DONE

UI

  • Fix Welcome loading
    • skip "loading" or make it nicer
  • icon on join game button
  • 2x3 grid of words on spectate page
  • breadcrumb nav
  • use form labels (instead of just placeholders)
    • materialize style animated to show both?
  • smaller headers
    • spectate header especially is bad
  • integrate error handling
  • favicon (and updated manifest etc)

BUILD

  • switch to elm-live instead of elm-reactor with hot reloading for frontend dev server (still use something for local API)
  • PROD-ready
    • CloudFront
    • static assets in a bucket
    • domain and cert
  • codepipeline / codebuild / codedeploy CI

GENERAL

  • enforce at least one other player on game start
  • Rejoin doesn't work for buyer!
  • non-lifecycle errors are sticky
  • additional navigation (e.g. leave game / rejoin from welcome)
    • (see also "breadcrumbs, above)
  • improve error messages for users
  • display fixes
    • mobile zoom
    • show own name
    • show game name
    • unclickable self
    • display own points
    • display other players' points
  • flow fixes
    • back from create/join
    • back from bad game code (failed join)
  • flow fixes
  • styles (materialize)
  • cannot become buyer if someone else is?
  • dev server with assets
  • varying poll interval (depending on lifecycle)
  • better join mechanic
    • prefix support in API
    • find unique prefix in API ( -> model)
    • prefixed game key display
  • refactor views
  • join game, password? (if required)
  • loading pages over last page
    • wipe a curtain with a stanley picture or something
  • design UI as a game
  • loading pages use vdom!
    • starts with same headings etc as target page, spinner that loads content. Swaps content in when ready.
  • stop being buyer without awarding point?

  • elm SPA frontend

    • create / join
      • create takes password
      • QR code to join? Or tapphones with Android beam?
      • join scans QR code, inputs code?
    • joiners put their screenname in
    • creator arranges joined people in order
    • configures game (e.g. time limits)
    • creator 'starts' which deals cards into the game state
    • hits lambda backend for application state reads / updates

  • S3 state

    • /prefix//game.json (GameState)
    • /prefix//.json (PlayerState)
    • stores JSON blob of game state, which contains player keys to look up player data
    • there's a race condition on registering :-/
      • Could write players only when the game starts, using ls? <- this sounds sensible
    • players, player cards, player scores (and won cards), current product
    • also player's previous cards so they aren't re-dealt
    • only things that affect other player's rows are awarding win and passing the pitch I think?

  • Lambda backend

  • hard-coded list of roles and words as jar resource?
  • lambda randomly deals out of this

Ensure:

  • ALL data auto-deleted after a couple of hours?