1. SwipeMe Abhijoy Saha - Jason Zheng - Kevin Wu - Kyle Nguyen
- Michelle Doelling - Richard Sun
2. Purpose Why is SwipeMe needed? Why would it be successful?
What makes it different?
3. Logging In
4. Selling Swipes Post Listings with Customizable Options Users
Search For Your Listings Potential Buyers Contact You
5. Selling Swipes Creating An Offer
6. Buying Swipes Deleting An Offer
7. Buying Swipes Select restaurants to dine at Search listings
with custom time range View details for each listing Message
sellers for an exquisite meal on the hill
8. Buying Swipes - Selecting Restaurants
9. Buying Swipes - Search Listings
10. Buying Swipes - View Details of Listing
11. Buying Swipes - Message Sellers
12. front end - UI Simple. Clean. Mouth-watering. Flat design
for a modern look. Easy-to-understand layout. Vibrant colors and
images. User Interface Design
13. front end - UI Parse database Users, Offers, Messages
Backend Design
14. front end - UI Created during first login Facebook User ID
Authentication Data Facebook First Name Backend Design - Users
15. front end - UI Created during Offer Posting - Sell Activity
Seller ID Restaurants Time Range Quantity Price (each) All offers
are deleted at 4AM each day using Parse Background Jobs Backend
Design - Offers
16. front end - UI Problem: Parse is good at storing and
retrieving data, but it sucks at connecting users in real time.
Solution? Sinch - Messaging Service Instant Messaging between users
Backend Design - Messages
17. Challenges Android Studio and Android SDK Messaging API and
Integration
18. Limiting Factors Dynamic Dining Hall Schedules Primitive
Time Filtering Facebook and Android Exclusive
19. Future Features Payment API Integration Expand to Other
Schools Location Dependent Check-In System Self-relying User
Database Editable Listings Sort Listings with Various Criteria
