---
# System prepended metadata

title: 'Dating Application: How does LOVE work?'
tags: [' computational thinking', mstu5003, ' lab']

---

---
tags: mstu5003, lab, computational thinking
---

---

# Dating Application: How does LOVE work?

Different applications have taken this simple premise and expressed it in very different ways. For example, think of different dating applications e.g. Match.com, Tinder.com, Bumble.com, OKCupid.com etc. Each has broken down their hypothesis of how love works (or ought to work) and expressed the phenomenon of FINDING love based on their hypotheses. You might even have your own competing twist on how you think love or finding love should work.

## SUB-Challenge

Everyone deserves to be loved. Pick a more specific population and their needs. E.g. elderly folk, introverts, lonely professors, etc. Using this specific population - think computationally on how love would work.

### Decomposition: Break down problems and phenomena into smaller multi-step parts.

- Break apart how you think "love" in online spaces happens.
    - What are the STEPS necessary in the process of a dating application?
    - What are the major PARTS of an online dating process?
- How does this relate to what you need to build in an application?

### Pattern Recognition: Analyze similar objects, phenomenon, and identify commonalities.

- Think about similarities between USERS and between parts of a SYSTEM:
    - What are some common things across USERS that are important to expressing the core idea of how you think love can be found?
    - What are some common things across the SYSTEM that are important to expressing the core idea of how you think love can be found?
- How would you express similar ideas in different parts of your application?

### Abstraction: Focus on relevant and important info / features. Separate core info from superfluous details.
- In simplest terms - what are the MOST important types of data needed for your application to work?
    - How are you going to get this data?
- What are the LEAST important pieces of information / features that you've come up with so far?

### Algorithms: Design sequential rules, ordered actions to solve the problem. Think about how each action results in a specific effect.
- Step by step how does the process of your dating application unfold?
    - In describing step by step - reference the data you would have collected, how that data would be used, and how the system would react to that data.
    - Challenge: How detailed can you be in describing your algorithm?
- Feature A:
```
- User does this
- System does this
    - System then does this
    - System then does this
    - System then does this...
- User does this
- System does this
```