:point_up:Kind of related to the above, and now th...
# confetti
m
☝️Kind of related to the above, and now that the spring conference season is officially over, I’m planning to revamp the networking/cache layers. Things I’d like to do: • anonymous bookmarks with offline support. Probably backed by a local store and some
WorkManager
magic to persist to the server when network is back. • fix the speaker detail bug where the cached result is replaced by an error. • more generally, make a pass at how we handle pull-to-refresh vs caching. I’m almost sure we have other similar bugs in the app. • trim down the server. I have been playing with KSP to write a reflection-free graphql server that should start faster and generally use less RAM than the current one. • improving the testing story. This is something that has been bugging me for a while with Apollo. Not 100% sure yet what shape it’ll take but something I’d like to look into.
👍 2
1
y
I think there is or was a test for work manager in the wear code
👀 1
👍 1