I had thought about adding move but decided not to. You can effectively move values by changing them. There are only a few. Once you have it setup, you won’t change it. Well this is the case for me.
Again I like to justify every addition to Flowx.
“Moving Values”, hasn’t been requested much, you can still effectively move values and it doesn’t add much value to the app.
As a contrast, “accumulated precipitation” is requested a lot, you cannot do it at the moment and adds value to the app.
I’m trying exemplify my thought process in justifying features in the app. Keep it simple.
I know I harp on about it but when I started Flowx, I added nearly everything users asked. Many of these features ended up being used by only one or two users, very occasionally, yet carried a lot of cost in terms of code maintenance and confusing users. Flowx was a mess. It felt like a straw house help together with duct tape. I would add a window (feature) and the door would fall off.
Keep it super simple.