I don’t disagree but I didn’t get any of that from that opening statement. It seems to be arguing for diversity in UI which I happen to think is usually a terrible idea.
> It seems to be arguing for diversity in UI which I happen to think is usually a terrible idea.
I have to agree with this sentiment. I loved KPT, but that was more for the "adventure" aspect. I actually had difficulty using a lot of functions (don't ask me to remember which ones).
It's frustrating, designing innovative UI that also follows convention. It's a joy, when it works.
I have this iOS widget that I wrote[0]. It's really, really cool. Works a charm, and is easy to implement.
But I keep on not using it in my projects. It's too "in your face." I think that UI needs to get the hell out of the way, and just let the user do what they want to do.
I have a couple of more, more conventional widgets, that I use all the time[1], [2].
KPT was "in your face," like no other UI I have ever experienced.
I have to agree with this sentiment. I loved KPT, but that was more for the "adventure" aspect. I actually had difficulty using a lot of functions (don't ask me to remember which ones).
It's frustrating, designing innovative UI that also follows convention. It's a joy, when it works.
I have this iOS widget that I wrote[0]. It's really, really cool. Works a charm, and is easy to implement.
But I keep on not using it in my projects. It's too "in your face." I think that UI needs to get the hell out of the way, and just let the user do what they want to do.
I have a couple of more, more conventional widgets, that I use all the time[1], [2].
KPT was "in your face," like no other UI I have ever experienced.
[0] https://riftvalleysoftware.com/work/open-source-projects/#RV...
[1] https://riftvalleysoftware.com/work/open-source-projects/#RV...
[2] https://riftvalleysoftware.com/work/open-source-projects/#RV...