Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roaming settings are deprecated #81

Closed
veler opened this issue Nov 27, 2021 · 3 comments
Closed

Roaming settings are deprecated #81

veler opened this issue Nov 27, 2021 · 3 comments
Labels
bug Something isn't working enhancement Idea of improvement of existing feature. help wanted Extra attention is needed

Comments

@veler
Copy link
Collaborator

veler commented Nov 27, 2021

Describe the bug
As mentioned here: https://docs.microsoft.com/en-us/windows/apps/design/app-settings/store-and-retrieve-app-data#roaming-data

image

Solution proposal

As a reminder, we're trying to avoid using the "internet" capability of the app, so users can "trust" this app for not sending anything over internet by default.

  1. Don't use Roaming settings

    • Pros:
      • No need of the "internet" capability in the app.
      • Cheap to fix.
    • Cons:
      • Less convenient for users
  2. Make a custom prompt asking the user whether he wants to use internet features or not. Then use OneDrive integration or Azure App Service to synchronize settings.

    • Pros:
      • Not too complicated to implement
    • Cons:
      • Requires some new nuget package, increasing the size of the app package
      • Internet capability is required even if user doesn't use internet features.
  3. Use an app add-on

    • Pros:
      • (to verify) The basic DevToys app won't need the internet capability.
      • User can optionally install an add-on that brings internet features, like roaming settings or tools that need internet.
    • Cons:
      • This will likely increase the complexity of the app.
      • We will probably need to "advertise" these add-on into the app, and users may be frustrated by what looks like a jerky app displaying ads.
  4. Add an Export/Import button like in the app Files https://www.microsoft.com/store/productId/9NGHP3DX8HDX

    • Pros:
      • User can export the settings and import them on another machine.
      • No need of internet capability.
    • Cons:
      • User must do it manually.
@veler veler added bug Something isn't working enhancement Idea of improvement of existing feature. help wanted Extra attention is needed labels Nov 29, 2021
@expikr
Copy link

expikr commented Jan 20, 2022

I think for a "lightweight offline app" like these, generally the user would expect a predictable initial state in any fresh installations.
This might also be the main motivation behind MS removing roaming profiles for UWP as well, because typically people expect "a simple UWP utility" not to retain any statefulness between machines.
Therefore it is a standard expectation that configuration states are self-contained and manually transferred, and may in fact be subconsciously desired by the user to trust the "dumbness" of the app not to have unpredictable behaviour.

@jwfxpr
Copy link
Contributor

jwfxpr commented Jan 20, 2022

Therefore it is a standard expectation that configuration states are self-contained and manually transferred

I agree, for a tool aimed at developers who are used to configuring a development environment to suit a purpose, I would expect to manually transfer configuration — and I would expect an easily readable and editable file, to customise config before importing if necessary.

@veler
Copy link
Collaborator Author

veler commented Mar 18, 2023

Super low priority and no good option at the moment. Closing for now.

@veler veler closed this as not planned Won't fix, can't repro, duplicate, stale Mar 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement Idea of improvement of existing feature. help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants