Importance of Fitness Activity and Sleep Tracking Apps in this pandemic

Is using getx's `ever` function a code smell? I'm using getx as a library rather than a framework ie state management instead of wrapping the app in it and using their widgets

My background from writing reactive code in vuex is that whenever a watched variable in the overarching store is updated, it automatically calls its listeners and re-renders the view. However, my flutter widgets remain stagnant except I explicitly mount the ever worker and call setState on a local field basically duplicating the store variable/field. It feels hacky to me tbh and leads to errors about calling setState on non-mounted screens, which I'm circumventing by checking if mounted (another hack)

It feels contrived like Band-aid over an actual problem. Is there a more natural way to propagate changes? I'm neither using getBuilder nor obx cuz a significant portion of my code entails computing stuff rather than just outputting data off an api. I want ui decisions to reside on my statefulWidget rather than migrating them to getx controller

Is this really how the project functions, should it be used a specific way, or am I missing something?

Artificial Intelligence (AI) is redefining mobile app development, offering unprecedented opportunities for innovation and efficiency. In this article, we delve into how AI is transforming the way apps are designed, developed, and deployed. From personalized user experiences to predictive analytics and advanced security features, discover the myriad ways AI is enhancing mobile applications. Whether you're a developer looking to integrate AI into your projects or a business aiming to leverage AI-driven apps, our in-depth guide provides valuable insights. Stay ahead of the curve with The App Journey! Visit now!