🚀 New Package Released on Pub.dev: app_settings_checker 🚀

We're excited to share that our new Flutter package, app_settings_checker, is now live on Pub.dev! 🎉

This package allows you to easily manage and interact with system settings on Android and iOS, making it simple to:

🔋 Check and manage battery optimization settings
📍 Check and manage location settings
🔔 Check and manage notification settings
⚙️ Access app-specific settings
📱 Retrieve device information like model and ID

💻 Key Features:
✅ Easily open battery optimization, notification, and location settings
✅ Check if battery optimization is disabled
✅ Retrieve app version and device info

Check it out here: app_settings_checker on Pub.dev

https://pub.dev/packages/app_settings_checker

Happy coding! 🚀

#Flutter #AppDevelopment #FlutterDev #FlutterPackage #MobileDevelopment #OpenSource #AppSettings #BatteryOptimization #iOS #Android

Today's tip that I should start this mini-series with🎯.

The last two days it was about using different providers instead of the default one. But using (or I should write adding) different provider does not mean ditching the old one. We can add many of them and settings will be merged together. The order is important though. We will get different setting value if we register them in different order (assuming they all have it defined).

The last registered provider's value will win. See the following example 👇

Docs 📑: https://learn.microsoft.com/en-us/dotnet/core/extensions/configuration-providers

#dotnet #appsettings #providers

Today's tip will be helpful if you need to avoid relying on external sources for configuration.

Files are good for storing the values for production needs but are not the best if we need to read those in our integration tests.
External dependency in best scenario will be slow and in worst one it could lead to errors ❌ in tests that would not be problems in the logic that we test.

In such scenario Memory provider is useful. We can initialize it with a collection of KeyValuePair-s and we are good to go ✅.

See the attached example 👇.

Docs: https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-8.0#key-per-file-configuration-provider

#dotnet #configuration #appsettings

appsettings.json is a standard file that holds application configuration but it's not the only one. There are multiple providers and one of them allows to have configuration per file?

To enable it use builder.Configuration.AddKeyPerFile(Directory.GetCurrentDirectory()); and make sure the files names are the same as your configuration sections. If needed replace ':' with double '_'.

See the attached example 👇.

Docs: https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-8.0#key-per-file-configuration-provider

#dotnet #configuration #appsettings

Strongly typed configuration in #dotNET - the #AppSettings class by Bojan Veljanovski
#IConfiguration #Settings https://bojanveljanovski.com/posts/access-dotnet-app-configuration-using-a-strongly-typed-class/

A good #QualityOfLife #tip I have on here is going to #AppSettings, then #CollapsedToots and checking the boxes for Media, Replies, Lengthy, and Notifications.

It makes browsing your #Home and #Local #TimeLines so much easier.