[Frontend] The order of things

What comes first, second, and Nth on this project...

Poll Created Sat 9 Dec 2017 12:17PM
User Journeys -> Wireframes -> Design -> Build -> Repeat Closed Sun 10 Dec 2017 6:13PM
[EDIT: this proposal relates to front-end only]
Hey everyone, I would like to test the water on this issue. This weekend is a hackathon, and so the temptation is always towards wanting to build something by the end of it.
I want to propose a different, more methodical route - one which might mean very little code is written this weekend! That is:
User Journeys -> Wireframes -> Design -> Build -> Repeat
Results
Results | Option | % of points | Voters | |
---|---|---|---|---|
|
Agree | 100.0% | 5 |
![]() ![]() ![]() ![]() ![]() |
Abstain | 0.0% | 0 | ||
Disagree | 0.0% | 0 | ||
Block | 0.0% | 0 | ||
Undecided | 0% | 21 |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
5 of 26 people have voted (19%)

Keith Lim
Sat 9 Dec 2017 3:53PM
Made some wire frames / interaction prototype...
check it out: first user journey being search and drill down...

Matthew Parsons Sat 9 Dec 2017 12:48PM
@hugi - great, taking that into account, I've modified the proposal to relate to frontend only. I think it does make sense for people to be hacking away on the backend and data layer (GraphQL/Apollo/Neo4j). All that familiarisation work is really valuable.
Hugi Ásgeirsson · Sat 9 Dec 2017 12:32PM
Well, we actually have a reasonably large team. Broadly I agree, but I actually think we have bandwidth to start working a bit in parallell. Some of the conceptual work groundwork for journeys and wireframes has been outlined here:
bit.ly/realitiesboard
We wen't through some of this yesterday over here last night.
Right now, @belaldabous, Robin, @fredrikbranstrom1 and @kidsthesedays have started talking about wireframes and design. There are some ideas in the air. I think you should sync with them on that.
As for backend, I think we have the resources to start setting up groundwork for the API structure. Things like setting up the DB, understanding how to get it to communicate with GraphQL/Apollo and serve to React. We're experimenting with that right now.
Also, Liam has populated a Neo4j database with the example nodes and relations from the whitepaper graph.
So, to sum up, while I broadly agree with this route, I think that we can multithread and get some substantial coding done this week.