Public Access
doc(requirements): assess things done to those intended
This commit is contained in:
@@ -1,10 +1,10 @@
|
||||
- running mobile app
|
||||
- users should be able to
|
||||
- plan public transport in the VBB transit network
|
||||
- create and customise routes quickly and on-the-fly
|
||||
- edit routes from anywhere, where respective route information can be seen
|
||||
- compare routes easily, especially between different endpoints
|
||||
- the app should offer up the information most relevant to current route planning
|
||||
- between route steps, there should be no more than 3 taps required, optimally even just one(1), scrolling excluded
|
||||
- e.g. only lines that connect to a station should be shown
|
||||
- stations that a line goes through should be available as next node/ step for planning
|
||||
- [x] running mobile app
|
||||
- [ ] users should be able to
|
||||
- [~] plan public transport in the VBB transit network
|
||||
- [~] create and customise routes quickly and on-the-fly
|
||||
- [ ] edit routes from anywhere, where respective route information can be seen
|
||||
- [ ] compare routes easily, especially between different endpoints
|
||||
- [~] the app should offer up the information most relevant to current route planning
|
||||
- [x] between route steps, there should be no more than 3 taps required, optimally even just one(1), scrolling excluded
|
||||
- [x] e.g. only lines that connect to a station should be shown
|
||||
- [x] stations that a line goes through should be available as next node/ step for planning
|
||||
Reference in New Issue
Block a user