We need to look after our staff, their wellbeing, their families and loved ones. Here at HRSimplified, we have implemented remote working as a strict policy and now adhere to the instructions from the Government. It is important to implement Social isolation as quickly as possible, if you have not already implemented this at your business, please do so as quickly as possible.
Some of the guidelines regarding what this means can be found on the Corona Virus blog. The 2020 COVID-19 (Corona Virus) has presented a work from home situation and it is important to follow the rules laid out by the South African government regarding the implementation of the Disaster Act. That said, I find Flutter is at least relatively easy enough to implement things that you can't find from the ecosystem.Guidelines for Working from home for your Business
#Stretchly skip current break code
I too explored a mapping project using it a year or two ago now and ended up having to essentially create my own map view using mapbox APIs (unfortunately I don't have code that I can share from that project). The libraries on pub.dev can be very hit-or-miss, and I definitely wasted some time trying various libraries from there before either giving up or rolling my functionality. You're right that it is definitely still rough in some places though. I think its killer features are the cross-platform support by default and the hot-reload-I found the hot-reload functionality so invaluable that I ended up jerry-rigging hot-reload into my current product at work. I haven't done a huge amount of UI development work in my life, but of the things I have used, I have found Flutter to be far and away the easiest to quickly express the UI you want to build and just build it.
But if you want to use it or fork it for your own purposes, please do. In any event, this is an app I made for myself. My biggest take away from all of this is that the work required to create and manage a store presence (localization and especially localized screenshots) is almost an order of magnitude more work than programming the damned thing in the first place. I also decided to localize it (using Google Translate) for the experience of doing so.
I also decided to publish the app and use it as a learning experience-I've worked on parts of mobile apps before, and developed proof-of-concept mobile apps before, but I wanted to follow the process through from start to end. Since time tracking is fairly simple, I decided to write my own app to scratch my own itch. Many necessitate sending data over the network for multi-device sync-a feature I have no need of, but can never disable. I've tried numerous time-tracking apps on the app stores, but they've each fallen short for me in some way or another-many are too complicated, or don't _just work_, or cost more than I think is reasonable. I hate time-tracking, but it is a requirement of my job (grants that help pay for my job, really) and if I don't have an app handy, I tend to forget to record my time. I was recently inspired by a post on HN: “An app can be a home-cooked meal” and decided I was finally done putting up with time tracking apps that didn't suit my own use case well enough.
0 kommentar(er)
