Functional Overview
In the first iteration of the service, referred to as the “Prototype”, users will be able to take a photo from within the application on the camera phone, and upload that photo and date taken to a main server, and from there distribute the photo to a specified group of users. When these target users open up their “Prototype” midlet on the phone, the uploaded photo will be displayed along with the date of the photo.
Recipients and senders – both also known as users – can:
1. View new photos upon entering the midlet. These are photos which others have uploaded and
shared with the user.
2. Take a new photo, to be uploaded to the server, and shared with a group of users.
Process Flow (Reference Addendum section for the Figures):
1. When the sender wants to create a new photo, he clicks on “New Photo” button from the main
menu. (Fig. 1)
2. The sender takes the photo on the camera phone by clicking the “Capture” button. (Fig. 2)
3. The sender clicks either the “1” key on his mobile phone’s keypad to “1) Save & Upload” or the
“Save” button to upload the photo to the server. (Fig. 3)
4. When the recipient(s) launches the application and clicks the “View Photos” button (Fig. 1),
they are presented with a new message to display the new photo. (Fig. 4)
5. The recipient(s) can choose to display the new photo(s) and click “Next” to view the next new
photo(s). (Fig.5)
Assumptions
1. User already has a PeerShopper ™ account
2. Users have a camera phone – (Motorola v3xx and other popular J2ME phones)
3. Users can download midlets to their phone (receive and display pictures)
4. PeerShopper database (PS db) to be created from scratch