You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a SPA, currently using Next.js. Right now user data is stored on a server.
I'm going to move to local-first, so the app will work without a network connection, and the user only needs to login if they want to sync their content with the server. And obviously I want to wrap this with Tauri to allow native installs. User data will be stored in LocalStorage for PWA users and on the filesystem for Tauri users.
Any recommendations for architecture? For example, I could split my existing Next.js project into two projects, backend (Node) and frontend (React+Vite.) This is kind of a hassle since there's a good deal of shared code, but seems inevitable. Is there a better idea?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a SPA, currently using Next.js. Right now user data is stored on a server.
I'm going to move to local-first, so the app will work without a network connection, and the user only needs to login if they want to sync their content with the server. And obviously I want to wrap this with Tauri to allow native installs. User data will be stored in LocalStorage for PWA users and on the filesystem for Tauri users.
Any recommendations for architecture? For example, I could split my existing Next.js project into two projects, backend (Node) and frontend (React+Vite.) This is kind of a hassle since there's a good deal of shared code, but seems inevitable. Is there a better idea?
Beta Was this translation helpful? Give feedback.
All reactions