Seems pretty useful to be able to write your documentation videos as steps and generate new videos everytime the platform changes. Let’s say you have 200 videos showing how to do different things and now the UI changes.
You can either leave the videos as is (and get more confused customers) or you can spend a lot of hours recording 200 videos again. Or you can run this and get the 200 videos done in the background. Let’s say that your app is changing every month because you are early in your iteration. That is a lot of time saved every month.
Say you have documentation with a video showing the user how to open a page, click a button, scroll, etc. Instead of having to re-record those videos every time you update the UI you can use this library to automatically recapture it on every push.
Firstly, you had to pay so much money for that screen that you had to consider buying a new device.
Secondly, Apple Products seem specifically engineered to easily break catastrophically (see SSD power supply below speaker grill, zapping the NAND modules if liquid enters the conveniently placed holes. Or a loose metal plate slicing a crucial ribbon cable when the phone was dropped. And many more such cases
This mix of overly fragile design and ridiculously expensive first-party repairs combined with parts pairing and the resulting inability of third-party, non-apple-certified repair shops to level the playing field is what I call a scam.
Same goes for a Fairphone
reply