I agree, designing for 3D printing and more specifically designing for multi-color or multi-material can help save a lot of time and material.
Additionally, printing any number of copies of the same multicolor object will result in the same amount of waste. This doesn't reduce the absolute amount of waste, just makes it a smaller % of the total material used.
Also worth looking into the "wipe into object" setting in the slicer, which will use the color changes in an extra model instead of purging them.
That has been my experience as well. I had a bunch of printers before the X1C, from 3 different countries, and all of them needed various amounts of tweaking and hacking to reach the print quality and ease-of-use I was expecting.
Even the Prusa MK3 (upgraded to MK3S, then MK3S+...) required a Raspberry Pi to be able to print without lugging an SD card from my PC to the printer, and a USB webcam to add print monitoring.
Now when people ask for FDM printer recommendations, I tell them that this hobby has two main paths: One path regards the printer as a tool to create things for other projects; the other path has the printer as the project itself.
An analogy I use is buying a car that's working and ready to drive vs buying a car that doesn't work and repairing it. Are you looking to drive or are you looking to fix/build a car?
Bambu printers are an easy recommendation for a printer which is a tool. The new Prusa CORE One might be a good fit as well, but it's still too early to tell what its quirks are. For printers that are projects, the Ender 3 comes to mind as a very cheap base for countless tinkering and upgrades.
The part about Android actually applies to all mobile operating systems - they would all rather you'd use their native UX language than invent your own.
I'd like to stress that this is the correct solution. It is not enough to just slap on a "left-handed mode" that mirrors the UI. Most left-handed people don't use just their left hand when operating their phones - they use both, but prefer their left.
> Depending on your target audience, strive for accessibility, create layouts that can be used while e.g. driving, try to make your application adapt to the environment (for example mind the time of the day)
Spotify (at least the iOS version) does this both wrong and right.
When you browse for music, the app offers playlists based on the time of day. This is great, as the time of day has a lot of influence on the mood you'll want your music to convey.
On the other hand, player view got one thing wrong. In this view, you can swipe down anywhere to exit the player view - as the player is "minimized" when you're browsing for music. However, swiping down anywhere really means anywhere - even when you're trying to skip the current song, and your finger happens to move down a little (maybe because you're driving), it minimizes the player rather than skipping the song. The minimized player is a smaller touch target than the playback icons, which makes returning to the player view and ultimately skipping the song extra-hard.
As a person currently in the process of deploying a graphite-based monitoring solution, this is extremely relevant. Grafana was looking very promising but I was intimidated by the installation process, so I skipped it. This looks like a great solution for me. Thank you!
It's unfortunate that newer cars are not supported.