---
# System prepended metadata

title: 'Unit 10:Deliverable Milestone - README Example'

---


Unit 10:Deliverable Milestone - README Example
===
### Milestone Deliverables###
## Week 10
## Milestone Deliverables

* Updated status of issues in Project board (yes)
* -Developed the appearance of User Interface 
* -Builded the appearance of the buttons,textfields,register buttons,label and other elements
* -Implemented constraints ,and auto layout to the cover
* Sprint planned for next week (Issues created, assigned & added to project board) (yes)
* -Develope the behavior of user interface
* -Develop registration function,
* -Develop entire backend
* Completed user stories checked-off in README (yes)
* Gifs created to show build progress and added to README (yes)

https://imgur.com/mL4e8aD 



# SeniorBook

## Table of Contents
1. [Overview](#Overview)
1. [Product Spec](#Product-Spec)
1. [Wireframes](#Wireframes)

## Overview
### Description
SeniorBook will be a social networking platform for Seniors who reside in Senior Homes (in particular for Senior Homes in USA). 

### App Evaluation
- **Category:** Social Networking 
- **Mobile:** This app would be primarily developed for mobile but would perhaps be just as viable on a computer, such as Facebook or other similar apps. Functionality wouldn't be limited to mobile devices, however mobile version could potentially have more features.
- **Story:** Analyzes users currently residing Senior Home, and connects them to other users with similar locations and interests. The user can then decide to message the person and be friend if wanted.
- **Market:** Any Senior home resident could choose to use this app, and to keep it a safe environment, people would be organized into age groups.
- **Habit:** This app could be used as often or unoften it all depends to the Users choice.
- **Scope:** The main goal of this app is to connect Seniors across the USA and give them the chance to socialize through different Senior Homes.

## Product Spec
### 1. User Stories (Required and Optional)

**Required Must-have Stories**

* User logs in to access previous chats and preference settings
* User will be able to keep and maintain a personal page containing information about their name, age, currently reside senior home, interests, and group memberships.
* User will have the option to upload photographs on their personal pages. 
* User will use the search function, former Senior home residents, or Seniors with the same interests will be found through the 15,000Senior Home across the USA.
* User will provide a private messaging service for its members, including a birthday reminder for people on their friends list.
* User will have the chat-function called “Chit-ChatRoom” .
* Matches have a chat window to get to know each other
* Profile pages for each user
* Settings (Accesibility, Notification, General, etc.)
* * One of the “SeniorBook’s” central functions will be the “live-love-laugh” .It is much like the poking function on Facebook where users can send each other notifications. 


**Optional Nice-to-have Stories**

* Page of most searched Senior Home (Senior Homes that most users are connecting through)
* Profile Add-On: Top Senior Home choices...etc


### 2. Screen Archetypes

* Login 
* Register - User signs up or logs into their account.
   * Upon Download/Reopening of the application, the user is prompted to log in to gain access to their profile information to be properly matched with another person. 
   * User needs to choose and register the Senior Home from the location finder
* Messaging Screen - Chat for users to communicate 
   * Upon selecting the Senior Home users matched and message screen opens
* Profile Screen 
   * Allows user to upload a photo and fill in information that is interesting to them and others
* Senior Home Searching Screen.
   * Allows user to be able to choose their desired matches of preference and begin interacting with them.
   * User can follow/unfollow another user
* Settings Screen
   * Lets people change language, and app notification settings.

### 3. Navigation

**Tab Navigation** (Tab to Screen)

* Senior Home selection
* My matches selection
* Profile
* Settings
* My Photos
* Private Message

Optional:
* Discover (Top Choices)

**Flow Navigation** (Screen to Screen)
* Forced Log-in -> Account creation if no log in is available
* Profile -> Text field to be modified. 
* Login Screen ->Home
* Registration Screen ->Home
* Stream Screen ->None, but future version will likely involve navigation to a detailed screen to see * comments for each photo.
* Creation Screen
* Home (after you finish posting the photo)In the actual wireframe, you will need multiple screens to represent the creation process to add filters, etc.
* Search Screen  None



---

Schema 

Models

---
Post
| Property     | Type     | Description |
| --------     | -------- | --------    |
|ObjectId      | String   | unique id for the user post (default field)         |
|author        | Pointer to user |image author   |
| image        |  file        |   image that user posts          |
| Caption      | String   | image caption by author     |
| CommentsCount| Number|number of comments that has been posted to an image   |
| likesCount   | Number         |   number of likes for the post          |
| CreatedAt    | DateTime     |date when post is created (default field)       |
| UpdatedAt    | DateTime|date when post is last updated (default field)   |


Networking

*List of network requests by screen
Home Feed Screen

*(Read/GET) Query all posts where user is author

*Create/POST) Create a new like on a post

*(Delete) Delete existing like

*(Create/POST) Create a new comment on a post

*(Delete) Delete existing comment

*Create Post Screen

*(Create/POST) Create a new post object

*Profile Screen

*(Read/GET) Query logged in user object

*(Update/PUT) Update user profile image



---
An API Of Eldercare locator API

*https://eldercare.acl.gov/WebServices/EldercareData/ec_search.asmx
 Note : Requested the API to use it for this project
 
 

| HTTP verb| Endpoint | Description |
| -------- | -------- | -------- |
| get     | cities    | gets all cities   |
| get | /cities/byId/:id| 	gets specific city by :id|
| get     | states     | gets all states    |
| get | /states/byId/:id| gets all specific states by :id |
| get     | zip    | gets all zips    |
| get | 	/zips/byId/:id| gets all zipcode by :id |



