agati
BAN USER1. Understand the requirements, User flow
2. Data structures / modeling
3. Algorithm design / UI
4. Testing
1. Requirements: Address book web application, so the user comes to a website (login? fcbk/google login?) use fcbk/google login api? loads them up, info about each field
- name
- phone
- address
- email
- bla bla
Target users? segments of customers
Timeline of project / resources
technology (LAMP, servers etc)
Functional documents, wants / wishes etc
2. MySql DB, table of users, table of addresses
3. address page, login page, user dashboard -> addresses
4. UI manual tests, jasmin JS tests, Server stress tests, User feedback and A/B testing, browser monitoring, eventing etc
Two Options:
1. Cookies:
Issues with cookies include having it to be sent back/forth to the server over HTTP which adds to the bandwidth and is a security concern. Also limited to about 4KB which may not be enough for web applications use.
Domains have cookie limits, usually about 50 cookies per domain name.
How to use:
createCookie, deleteCookie and getCookie using the DOM with document.cookie, example at:
quirksmode.org/js/cookies.html
2. html5 LocalStorage:
Available across all browsers. Limit between 5mb to 10mb and doesn't get sent over http.
more on this here:
diveintohtml5.info/storage.html
Place all the icons into a sprite and this will reduce it into a single request. Using sprites can be done through background images
- agati November 03, 2012