-
Notifications
You must be signed in to change notification settings - Fork 0
/
todo.txt
21 lines (17 loc) · 916 Bytes
/
todo.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
TODO:
NOW
MEDIUM
LOW (nice to have)
- Custom domain
- If backfill succeeds but those activities aren't inserted, we need to be able to catch that error - store activity count alongside updating backfill_status?
- Explain when user has completed a trail
VERY LOW (maybe do at some point)
- Add user settings for units and activity types to include
- Check and respect rate limits to avoid overuse
- Email notification for when processing is done
- Show background processing completion on /trails/[id]
- Look into pulling streams and processing these in addition to polylines - is it really necessary? What's the max. privacy area on Strava?
- Check we meet Strava brand guidelines
- Dark mode
- Add activity browser/search in /account
- Consider checking athlete backfill/processing status on exchange to figure out where to redirect them to (could avoid /backfill flashing up if we check it before redirecting)