J
@mcc my first thought from a security perspective was to have all local data wiped and replaced with {user}'s data on login, or potentially segregating it by auth'd user locally (trusted shared device). Both of those break the offline-online flow for anything that's not synced yet so my next issue is do I automatically assign anything local to {user} when they log in, or should I ask for each item if they want to sync or delete?
Idk if paper to digital forms are an upgrade sometimes.
@mcc slightly different since its effectively an app rather than a website but this is something I'm trying really hard to avoid in the thing I'm building now.
Basically making it "offline first" store everything locally and try to sync in the background if you're logged in. Adds the user ID on backend when syncing with proper auth.
It's more effort but it would be nice to see people care about UX more.
@taurus @cmthiede @Natasha_Jay at that point the investors are doing the same thing to pump it up so they can sell it on to someone else so they're not holding the bag.
@cmthiede @Natasha_Jay in this case I thought what they're paying for was mostly plausible deniability and blame shifting when investors find out that the numbers you showed them were 20x better than reality.
