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
Developers as app publishers have a fission account and webnative filesystem. It should be possible for developers to use a per-app section of private storage.
The text was updated successfully, but these errors were encountered:
Is this where we go back to the idea of putting published apps in the file system? If so, where would you put them? We currently put application data in private/Apps/${appCreator}/${appName}/. Could we keep roughly the same pattern for this and put the apps in public/Apps/${appCreator}/${appName}/? 🤔 Not sure if that would clash with public app data though... Thoughts?
In the past we've talked about app cloning, so with this pattern a developer's apps could live side-by-side with their cloned apps. The idea behind cloned apps is that if you see an app you like and would like to freeze updates to it, you could clone it (and later still update if you want).
Just noticed that the dashboard puts them in public/Apps/${appName}/Published (correct me if I'm wrong @matheus23)
This should probably be public/Apps/${appCreator}/${appName}/Published/ to stick with the existing naming convention.
Developers as app publishers have a fission account and webnative filesystem. It should be possible for developers to use a per-app section of private storage.
The text was updated successfully, but these errors were encountered: