Meal sharing App Proposal

[bhas]

#124

This PR contains a proposal for how we can make the meal sharing app fit into the new curriculum structure.

It is easiest to read it here

[adamblanchard]

Thanks so much for writing this up! In general, i +1 this direction.

Great idea to separate the projects from the modules themselves, and tie them together with the learning goals.

Balancing what we provide vs what they build feels like a challenge (but a fine one to have). For example, if we provide a full UI with mocked data, ready to just be connected, how do we leave enough space for backenders to come up with their own solutions?

1. This mocked data might provide too much of an answer to how they design their data, would we rather they have an empty slate to design on?
2. If the UI only needs connecting to new endpoints, won't it give too much away (or be too restrictive) in the endpoints that the backenders have to create if we already must have some fetching code implemented in the frontend?
3. What if the backenders add some cool functionality to one of their endpoints (e.g. to recommend a movie), they then also have to implement the frontend to actually be able to show it as part of their deliverable. How can we give space to be creative but also not require frontend work to show it?

In general I like the idea of having a "full stack app" working at the end, since this also replicates what working in a cross funtional team would look like. It does add a lot more on us to provide the other half, and some restrictions to what they could implement, if they strictly only work on one side of the stack.

Just thinking out loud a bit, since this is a proposal.