Could you adjust the refresh frequency based on your usage patterns? So refreshing less frequently outside your main transit times. An extension of your current pause at night.
How rapidly has business software changed since COVID? Yet how many skyscrapers remain partially unoccupied in big cities like London, because of the recent arrival of widespread hybrid working?
The buildings are structurally unchanged and haven't been demolished to make way for buildings that better support hybrid working. Sure office fit outs are more oriented towards smaller simultaneous attendance with more hot desking. Also a new industry boom around team building socials has arrived. Virtual skeet shooting or golf, for example.
On the whole, engineered cities are unchanged, their ancient and rigid specifications lacking the foresight to include the requirements that accommodate hybrid working. Software meanwhile has adapted and as the OP says, evolved.
Twilio's Flex isn't far off this concept. For building simple voice and text message applications, it does quite a lot out of the box. It's their full telephony stack but presented at a much higher level of abstraction.
I'd like more tries to pick out the notes when pecking at the on-screen keyboard. I don't need to hear the pattern again, I need to learn where the note pitches are on the keyboard.
I can't see how half of the icon choices made in the article would pass internal testing, let alone actual user testing.
Maybe stakeholders were calling the shots and everyone was like, "Fine. If you want us to reuse the same icon for different purposes, you're the boss. We are done trying to explain why this is a bad idea."
Ahh, I get it now. Maybe you can improve the wording around this to make it less suggestive that your value proposition is I can change one cell when it fails. That's not safe. The value prop is I can change for a new set of cells cheaply when I get a failure in my current set.
You're going from when one cell fails, change the entire battery assembly, including any management electronics, case etc
To
When one cell fails, just get a fresh set of cells, at a fraction of the cost of a new battery assembly.
In the future, you also expect working cells to be circulated back into second-life use. Your casing makes this much more likely.
I'm confused why your value proposition is that you can replace individual cells but your website also says it's recommended to replace all cells at once. Isn't that the same as the current situation where we have to buy a new battery assembly rather than replace the failed cells?
> When an E-bike battery fails, 90% of the time, its just 1 or 2 cells that are dead inside or a single electronic component. But since traditional batteries are spot welded and glued, there is no chance to replace the faulty part and you need to replace the complete battery.The infinite battery is different. It uses a technology that makes it easy and safe to replace any parts, including lithium-ion cells. It doesn't require any specific tools nor knowledge. It takes less than 10 minutes.
> For safety and durability, it is recommended to change all cells at once.
We're a Ruby shop and we have pretty much zero commented code. Ruby's intended to be readable enough not to need them and when we do need them, it's a sure sign we need some refactoring.