For those who love to visit new place ,explore every part of the world before they die in short a travel enthusiast…medium.com
Now after selecting app idea my next job is to make a prototype of my web app using recommended platform proto.io , a…medium.com
As my application is more like a social networking website it’s data model is a little large
Mainly i required 6 table to capture my all data as shown in the screenshot.
On implementing Friends_relationship I am facing two options here:
- The typical case, where I will store both
user1 -> user2and
user2->user1. This will take more space, but (at least in my head) require just one pass over the rows to display the friends of a particular user.
- The other option would be to store either
user2->user1and whenever I want to find all the friends of
user1, I will query on both columns of table to find a user's friends. It will take half the space but (again at least in my head) twice the amount of time.
As the app should be 3 screens app i have to remove the friends review functionality and it makes my app more complicate to implement,also removed the restriction to choose from certain set of places as shown isn previous data model ,also update ui accourding to convenience.Now the data model looks like