Семён Марьясин
Instead move them to server-side (in auth.py) and send only to Google. Or maybe instead remove redirector page and move client id to config page's js (at last we anyway...
Maybe dynamically include session id in config page code and check it on auth.
When user launches app, after (during) loading of lists, set cursor to last-selected one. Also, maybe (?) remember selected task in each list? This will strictly require more consistent IDs...
Command to clean completed tasks from list (as in GMail's interface). Do we need it?
It may be possible that JS app will be killed while watch app is still running. We must handle this state, e.g. save anything important in local storage (like list...
This may help "use (window changing) animation to mask lengthy process", as in design guide. Also we might display cached data and later update them. Maybe ask Google for list...
Use more sophisticated ID system. Example: user opened some task from 3rd list; then a new list was inserted between 1st and 2nd. With current scheme ids will be messed...