2 ms·
Design for: * blind * def * reading impaired * other languages/cultures * slow/bad hardware/iffy internet To me at some point we need to g
by almosthere 1y ago
Design for:
* blind
* def
* reading impaired
* other languages/cultures
* slow/bad hardware/iffy internet
To me at some point we need to get to an LCARs like system - where we don't program bespoke UIs at all. Instead the APIs are available and the UI consumes it, knows what to show (with LLMs) and a React interface is JITted on the spot.
And the LLM will remember all the rules for blind/def/etc...
- bigstrat2003 1y agoThere are a whole lot of applications for which it makes no sense to design for other cultures. Not everyone is building something for a business which is, or might be, doing business internationally after all. Also I think until LLMs become reliable (which may be never), using them in the way you describe is a terrible idea. You don't want your UI to all of a sudden hallucinate something that screws it up.
- almosthere 1y agoLLMs don't hallucinate THAT badly, and if you're doing many calls for small pieces, it rarely makes those kinds of mistakes. As far as international emitting of interfaces - yes it absolutely makes sense to do it this way. If you're asking for an address and the customer is in the US, the LLM can easily whip up a form for that kind of address. If you're somewhere else, it can do that too. There's no reason for bespoke interfaces that never get the upgrade because someone made it overly complicated for some reason. Back in the day, AOP was almost a big thing (for a small subset of programmers). Perhaps what was missing was having a generalized LLM that allowed for the concern to be injected. Forgot your ALT tag? LLM, Not internationalized? LLM, Non-complicated Lynx compatible view? LLM