agree. for the use case that you mentioned there would be a problem. but as you said, it could be overcome by using native apis that store state. it's even imp

agree. for the use case that you mentioned there would be a problem. but as you said, it could be overcome by using native apis that store state. it's even imperative in case of secrets, like access tokens and the like. for client side web apps there's a bigger problem with localstorage. from my experience end users switch browsers and platforms. and they expect consistency from their web sites/apps. this expectation is much more intense than for native apps. so, while practical for developers, i'm not sure it's that welcomed in web land except for always having a local backup or as a temporary storage to alleviate network issues.