1809807 - Current wallpaper storage should be abstracted away from `Settings`

Status: NEW

(Firefox for Android :: Homepage, task, P3)

Description

[Chris Peterson [:cpeterson]]

From github: https://github.com/mozilla-mobile/fenix/issues/26033.

There should be an abstraction layer implemented to cover the usage of Settings to track the current wallpaper. This is with the goal of eventually porting the bulk of the Wallpaper implementation to A-C, where it can't be guaranteed that the storage layer is the same as it is in Fenix.

Create an interface that can define current wallpaper storage and add an implementation of that interface that uses settings under the hood as is currently done.

Note that this may require code to handle migrations to a different storage implementation down the line.

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Comment 1

[Aron]

If you mean that the storage of wallpapers should be abstracted away from the 'Settings' module, it could imply separating concerns related to wallpaper management and settings management. This separation might enhance modularity, maintainability, and scalability of the codebase.

Abstracting away wallpaper storage could involve creating a dedicated module or service responsible for handling all aspects of wallpaper management, including storage, retrieval, and manipulation. This can make the codebase more modular, making it easier to update or change wallpaper-related functionality without affecting the settings functionality and vice versa.

Without more context, it's advisable to follow best practices in software design and consider factors like modularity, maintainability, and scalability when making decisions about code organization and architecture. If you have specific technical questions or need guidance on implementation, feel free to provide more details!
https://hometownstorageunit.com/safe-and-secure-storage-rentals-mason-mi/