*User A when setting the connection will define a list of "prizes" and their cost in coins.

*User A when setting the connection will define a list of other users who can send coins to be as well, (user C,D,E,F)

Example:

Mother connection with Son.

Mother is user A.

Son is user B

Father is C.

Father is optional.

(user A) Mother will set up prizes such as "spent X time watching tv or playing games" for 50 coins among other prizes.

(user B) Son will be able to do real life chores and receive virtual coins through the app. He will store those coins until one day he can exchange them for prizes.

*User A (mother) should then approve such Prize exchange, therefore all purchases of prizes need a "pending approval" status until User A approves it.

*User A should be able to send coins to someone on his contact list who also uses the app, if not invite him to install the app.

*User B should be able to save those coins and one day exchange them for "virtual" prices that User A defined from day one.

*User B should be able to REQUEST COINS for a CHORE and user A receive a "pending approval of chore", no need of a predefine list of chores. Just a transaction where user B writes the string and the amount.

*Users (A,B,C,*) should be able to see from the main menu their prizes status:

-Pending approval (user A needs to approved)

-Approved (user B needs to use it)

-Redeem (user B already used it)

Main Menu:

*scroll HORIZONTALLY for CONNECTIONS

*the last screen should be (Set up a new connection) (if no connection is set , then first screen is set upa new connection)

Example:

*Connection #1 "Mother and Son" first screen

Scroll to the right, "Connection #2 Boyfriend and Girlfriend"

See Prizes and Send Coins would change when scrolling.

*Send Coins Button / or Request Coins for a Chore button

*View Prices

*Table with pending prices approval, redemption should be common for all connections. Can be static.