Be we spent a lot of time on that

Work plan

• Create simple dapp to display the favorite number and set the number using vanilla JavaScript + Bootstrap CSS
• Add references to README.md for any best practices followed or sources of any instructions (install steps, etc.) used
• Add screenshot to readme of working dapp (macOS + Safari, with shadows, PNG format)
• Add second screenhshot to readme showing interactivity, click the "Set Number" button and some visual feedback indicates the in-progress, and completed state (animated gif, I https://www.cockos.com/licecap/ to record)
• Complete instructions to deploy contract (mainnet, testnet, localnet, anything) and load wallet, load dapp, access in browser
  • Quality standard: one human that has interest in blockchain but zero experience programming, using a brand new 2019 MacBook Pro, successfully follows the instructions without assistance and reproduces the screenshot of the working dapp

IN SCOPE IS:

• File / class naming
• Separation of code into classes
• Which code should be autogenerated from AVM toolset (for type safety)
• Function names (should they prefix with AIPXXX)?
• Documentation
• Capitalization of words in documentation, and whether each line of documentation ends with a period
• Remove all build waarnings
• Should test cases access ABI encoders directly or should the have a type-safe data access object based on the interface for communicating with the on-chain instance?