Next, each user will choose the gender they are interested in. The same logic is used again to manage user preferences and expectations. As is usual with dictionaries, this one contains only one UNIQUE attribute, name. And again, the user will select the list of relationship type s they are interested in. Exchanging messages is the most common way. The three tables we need for this functionality are grouped in the Conversations subject area. The user who started the conversation will invite one or more users to it.

A list of all conversation participants is stored in the participant table. The last table in this subject area is the message table.

The order of the messages in a conversation could be determined using ts or id as the sorting column. Everybody wants to date, but nobody wants to date the wrong person. The first is having users grade each other. Maybe you liked their profile or had fun messaging them. Or maybe you met in real life and felt completely okay. Why not give a grade to that person?

It will record the ID of the user who gave the grade, the ID of the user who was graded, and the actual grade given. We could calculate the popularity of each user based on the grades they are given and how many blocks they have.

I strongly encourage you to go out and meet someone in person. If you have used some dating apps, which features did you like? How do you think these could be added to our dating app data model? Answered by timothybard 12 in a post from 13 Years Ago. This is my recommendation: Create one 'user' table that stores, at a minimum, UserId, but could also store name, DOB, etc. This table needs … Jump to Post. Answered by tesuji in a post from 12 Years Ago.

Hi like the beautiful ladies you are planning to manage there could be found so beautiful solutions on that web site. This table needs an ID field and a text field to hold the question Create an "Responses" table that stores the choices for each 'Attribute'. Let me know if you have any questions! Thanks for the input. I really appreciate it. thank you for help me in this area. I would like to make some more idea clear from you would you please help me more? Thank you in advance. Edited 12 Years Ago by nav33n because: Website snipped.

Do not spam, advertise, plug your website, or engage in any other type of self promotion. Read forum rules. its a very nice solution. Facebook Like. Twitter Tweet. Be a part of the DaniWeb community. Sign Up — It's Free! Reply to this Topic. This topic is old! No one has contributed to this discussion in over 10 years.

Are you sure you have something valuable to add to revive the existing conversation? Consider starting a new topic instead. Otherwise, please be thoughtful, detailed and courteous, and adhere to our posting rules. Edit Preview. H1 H2. Post Reply. Share Post. Permanent Link. Insert Code Block. Search Search.

Not cool. Not cool at all. Or maybe it will. How many dating apps can you name? I can think of at least a dozen. But we all need to start somewhere. These days, everything has gone digital — including dating, at least for the first few interactions. For any dating app, we need a way for users to register on our app, view and contact other users according to their preferences, and start a conversation with the lucky man or woman or men and women.

The rest is up to the users. We can assume that users will access our services either by a mobile app or our website. The most important part of this model is the User accounts subject area. Each user will create one account using their email address; that email, as well as other important details, are stored in this table. We have already mentioned gender. Besides the primary key, the only attribute in this table is the UNIQUE name attribute. Next, each user will choose the gender they are interested in.

The same logic is used again to manage user preferences and expectations. As is usual with dictionaries, this one contains only one UNIQUE attribute, name. And again, the user will select the list of relationship type s they are interested in. Exchanging messages is the most common way. The three tables we need for this functionality are grouped in the Conversations subject area. The user who started the conversation will invite one or more users to it.

A list of all conversation participants is stored in the participant table. The last table in this subject area is the message table. The order of the messages in a conversation could be determined using ts or id as the sorting column.

Everybody wants to date, but nobody wants to date the wrong person. The first is having users grade each other. Maybe you liked their profile or had fun messaging them. Or maybe you met in real life and felt completely okay. Why not give a grade to that person? It will record the ID of the user who gave the grade, the ID of the user who was graded, and the actual grade given.

We could calculate the popularity of each user based on the grades they are given and how many blocks they have. I strongly encourage you to go out and meet someone in person. If you have used some dating apps, which features did you like? How do you think these could be added to our dating app data model? What Do We Want to Achieve? Ready to dig in? The Data Model. Subscribe to our newsletter Join our weekly newsletter to be notified about the latest posts. You may also like. Read more.

The first is having users grade each other. The most important part of this model is the User accounts subject area. Next, each user will choose the gender they are interested in. This is my recommendation: Create one 'user' table that stores, at a minimum, UserId, but could also store name, DOB, etc. If a user is found to have 2 or more things in common they are alerted via email saying you have similarities with user A, B, C. For each user there is a profile some profile questions might be: nationality, education, age, eye color, etc, etc.. Why not give a grade to that person?

Categories:

• Dating sites
• Dating apps
• Best dating
• Free apps
• Dating website