-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathtasks.txt
177 lines (144 loc) · 4.8 KB
/
tasks.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
app initializes wrapper, so wrapper is the first screen
appview is the new wrapper
in appview: user data can be null, or it can exist
if user is null, user is not logged in and user is directed to the sign in screen
need to add a state and event to check for completed onboarding
NOTE decide what the default data for user should be.
the first check checks if the user has data.
if the user has data, it means they have at least been to the 2nd page of onboarding
(doesnt matter, bc you dont need default data you can save as you go) user has data means A user completed onboarding or B user has started but did not finish onboarding
if the user exists, onboarding can be null, false, or true
to summarize, user states in wrapper are:
A) user is not logged in
B) user logged in &&
a)user doesnt have data
b)user has data &&
I) user did not finish onboarding
II) user finished onboarding
The actions are
A) redirect to sign in
a) send to onboarding
I) send to onboarding
II) send to home screen
signin screen:
3 states
- user not logged in
- user logged in
- user begins automated google authentication flow
onboarding screen: stateless
2 user actions, skip and let's go
skip goes to milonamepicked and skips choosing and naming the buddy
go goes to choosebuddy
choosebuddy screen: currently stateful
- user doesnt have data
- loading
- user has data
- _currentbuddy == null
- _currentbuddy != null
- buddy is saved
- buddy is not saved
- data is sent
- data error
- currentbuddy image is set as an argument to choosename screen
choosename screen: currently stateless
- skip goes to milonamepicked
- milo goes to milonamepicked
- sky goes to skynamepicked
- arguement for image is passed to next screen as an argument
milo/skynamepicked screen: stateless
- arguement for image is passed to next screen as an argument
- only one button, 'save buddy' and goes to chooseactivity
chooseactivity screen: currently stateful
there's a lot going on here
there's no button, unless at least 3 activities are choosename
possible states:
- button disabled
- button enabled
- data sent to server
- data failed
- show loading?
- 0, 1, or 2 activities picked
- 3 or more activities picked
image arguments passed to next page
picktime screen: idk??? i really want to ignore this screen in favor of the core features
anyways
possible states:
- time picked
- no time picked
- save button pressed
- data sent
- complete dialogue pops up
- 'approve' button navigates to home
- data not sent
- loading?
home screen: stateful
possible events
- health going up
- health going down
- give milo treat
- show activities
- chooseactivity
- task added to list
- data sent
- data failed
- show loading?
- change buddy
bottomnavbar:
- just switches between screens
task screen
possible events
- task added to list
- task completed
- task filled in and disabled
- points data sent
- data sent
- data failed
- should uncompleted tasks be deleteable?
- should you be able to add multiple uncompleted tasks?
- decide which data should be persisted locally versus cached in the cloud
/NEED need a better way to check if onboarding is completed, bc the value can be null in between sign in and the first onboarding screen
/IDEA i think i need a user store for local data and not auth
/NOTES need to make the name a data object to persist along with the buddy image and save both in database
/REFACTOR make stateful widgets stateless
/CREATED activity bloc
/CREATED buddy bloc
/MAKEME name bloc
/NOTES refine models for data///
/PENDING
/FIXME
/COMPLETE
/BUG
/DUE
/CREATED
/DEAD
/REFACTOR
/URGENT
/NOTES
/NEED
/UNPLUGGED
/MAKEME
/IDEA
/1. [ ]
/2. [x]
/3. [ ]
/4. [ ]
/5. [x]
/6. [ ]
/7. [x]
/PENDING will mark miscellaneous,not urgent or important, or would-be-nice's
/FIXME issues that need to be fixed, code can't be released as is
/BUG Something is broken here, and i don't know what
/REFACTOR i can make this simpler, if i have time
/NOTE something i have learned, that i will need for the next time i code
/COMPLETE so i can remember what i did that day
/DUE i don't know, i guess if i have tasks on asana i can use this
/DEAD so i can remember what i can safely delete, and what isnt a work in progress or being used for testing
/URGENT this absolutely needs to be fixed right away
/UNPLUGGED a part of the code that ive been working on on the side, that still needs to be integrated into the app
/MAKEME a screen or some other feature i need to make still
/IDEA in case i get an idea about how to do solve something, but i can't do it right now
/[ ] this is what i will mark the days goals with
/[x] this is to mark a completed task that i set out to accomplish that day
/CREATED
/1. [ ]
/2. [x]