Quotes

Design and iOS Hack Project

Specification

This is a self contained project idea that is useful to assess someone’s skill level for building the diverse components required to create a fully functional, database driven, iOS application.

  • A list of quotes, sorted chronologically from the most recent to the least recent, that the logged in account can view
  • The logged in account can view all quotes that he/she either said or heard. NOTE: you cannot see all your friends quotes, you had to be there, either saying it or hearing it.
  • Tapping on a name takes you to the quotes that the logged in person can view that the name tapped on said.
  • There are 4 additional buttons: search on the top right, home (where you are), add quote, and profile.

(3 screens)

Search

  • When you tap search, the UI switches to top left above and places your cursor in the top left and bring the keyboard up
  • Typing in characters starts showing results by sending letters to the server and rendering matches that you can see (remember: only what you can see, which is what you heard or what you said).
  • Tapping return, dismisses the keyboard
  • Tapping cancel returns you home

Profile

  • The logout button enables you to test logging in as different users and ensuring that what you can see and search is appropriate.
  • For reasons you’ll see in the next set of mocks, we recommend login being a phone number and a password.
  • This page is the logged in user’s page. It has two tabs, “Said By” and “Heard By”, that show those items respectively.

(2 screens)

Add Quotes

  • This screen comes up with a user taps the quote button
  • As they type, the character count dwindles
  • To advance to the next screen, tap “QUOTE IT”

(3 screens)

Review

  • Has 3 new form entries, SAID, HEARD, and WHEN
  • SAID and HEARD will ask the user for contacts permission and then typing will match contacts (similar to typing in the to: field in gmail)
  • SAID can only be one contact
  • HEARD can be multiple contacts
  • When sent to the server, these will be stored with a phone number and a name. If every that next user joins (phone number + password + first and last name), the names can be normalized to the appearance that person wants. Before that happens, you should display them as they appear in your address book