CSE 135 Lecture Notes - Lecture 22: Gif, Social Proof, Json
4 Mar 2019
School
Department
Course
Professor
Document Summary
What the app did : collect: data to answer the question(s) Usually easier to just grab more than you need! Data client side w/ vanilla js: package data, transport the data, receive the data, store the data, scaffold the server side. Proof of concept of table/chart: build all the pages as stubs and mock the navigation. Finalize my app architecture: finalize authentication. Regular no user center (limit reports) Requires more work, but can provide additional functionality! Feature flagging - wrap everything w/ a ff. Make a call to is this allowed? (checks perms: user center. Crud applications! (add, edit, delete, list users) Look & feel : find a design pattern. Bulman: report - charts!, share report. Our sad experience this is the most common approach. Relying on the wisdom of the crowds . _ uses them, therefore it must be good! Our product isn"t the best solution for all viz problems. The truth is that no solution is a catch-all!
