31–40 of 51 posts
Great work! I like Material but this looks super slick and it feels like the documentation is more understandable. The design is really clean. I will consider this heavily when we upgrade our current ng1 app. Well done.
Hi Clarity team, What would you say the primary motivation in switching from material2 or ng2-bootstrap to clarity would be? At my work we have an Angular 2 app still in development and have been rather dissatisfied with the available component libraries so far. We're at a point where it wouldn't be unreasonable to switch UI frameworks. Additionally it looks like you have only implemented some of the material design…
Hi water42, I think material2 and other frameworks are fine frameworks and are worth your consideration. We really built Clarity because we were in your position. No framework out there was able to provide us with what we needed to ship high quality, enterprise software but with modern and consumer-like UIs. We needed that framework to care deeply about user experience (not just provide code) and we wanted to make su…
It would definitely be useful to publish the research behind the design choices you've made. As a developer with not a lot of design experience that's something I would be interested in.
Earlier quoted context omitted.
Hi water42, I think material2 and other frameworks are fine frameworks and are worth your consideration. We really built Clarity because we were in your position. No framework out there was able to provide us with what we needed to ship high quality, enterprise software but with modern and consumer-like UIs. We needed that framework to care deeply about user experience (not just provide code) and we wanted to make su…
Thanks for the quick reply! It would definitely be useful to publish the research behind the design choices you've made. As a developer with not a lot of design experience that's something I would be interested in.
Disclaimer: I am on the ng-bootstrap team The demo website loads very slow :( . I would recommend looking at https://ng-bootstrap.github.io/ for some code design of some of these components - as far as I can gather looking at the source code of Clarity, it appears to not be AoT-compliant, a big thing going forward with Angular due to the immense perf benefits it brings, and opens up the gate for also being able to us…
Hi Bahamut, welcome! we'd love to chat with you guys (feel free to reach out to me with a DM on twitter). We'd love to share what we learned and learn from what you learned! As for the slowness of the page, this is GitHub. It is currently down :( As for AOT, that's definitely a priority for us (we were talking about it as a team yesterday and are working hard to make it a possibility for Clarity so we're definitely o…
Earlier quoted context omitted.
Hi Bahamut, welcome! we'd love to chat with you guys (feel free to reach out to me with a DM on twitter). We'd love to share what we learned and learn from what you learned! As for the slowness of the page, this is GitHub. It is currently down :( As for AOT, that's definitely a priority for us (we were talking about it as a team yesterday and are working hard to make it a possibility for Clarity so we're definitely o…
ng core team here, feel free to reach out to me on twitter if you need any help getting this done - @robwormald
Earlier quoted context omitted.
Is it safe to say Clarity is for Angular 2 as what Blueprint ( http://blueprintjs.com/ ) is for ReactJS?
Hi wiradikusuma, for now maybe but when building Clarity we considered a future where we can have ClarityNG/ClarityReact/etc. However, for now, we're focusing most of our energy on ClarityNG to make sure we can deliver the next set of components to complete the library.
From first glance it appears that the form input elements on both of those projects are not going to be nearly as mobile friendly as I've found with Angular Material Design components.
I could very easily be mistaken, but already having a sense of what I feel like I need in order to make a nice mobile experience my first instinct would be to skip even trying out either of them for future mobile projects. That said, they both seem solid for building a standard web app the user will navigate with a mouse and keyboard.
Earlier quoted context omitted.
Hi wiradikusuma, for now maybe but when building Clarity we considered a future where we can have ClarityNG/ClarityReact/etc. However, for now, we're focusing most of our energy on ClarityNG to make sure we can deliver the next set of components to complete the library.
I have no experience with Blueprint, or for that matter Clarity, but I do have relatively extensive experience at this point with Angular Material components (NG1). From first glance it appears that the form input elements on both of those projects are not going to be nearly as mobile friendly as I've found with Angular Material Design components. I could very easily be mistaken, but already having a sense of what I…
1. To get more feedback on the docs if that's how you arrived there. 2. To get more feedback on the system itself (design and code) to see if there are bugs we can fix and issues we can improve.
Earlier quoted context omitted.
Is it safe to say Clarity is for Angular 2 as what Blueprint ( http://blueprintjs.com/ ) is for ReactJS?
Hi wiradikusuma, for now maybe but when building Clarity we considered a future where we can have ClarityNG/ClarityReact/etc. However, for now, we're focusing most of our energy on ClarityNG to make sure we can deliver the next set of components to complete the library.
Earlier quoted context omitted.
I have no experience with Blueprint, or for that matter Clarity, but I do have relatively extensive experience at this point with Angular Material components (NG1). From first glance it appears that the form input elements on both of those projects are not going to be nearly as mobile friendly as I've found with Angular Material Design components. I could very easily be mistaken, but already having a sense of what I…
Hi, ceejay! I'd love to know more about how you arrived to that conclusion. I am asking for a couple of reasons: 1. To get more feedback on the docs if that's how you arrived there. 2. To get more feedback on the system itself (design and code) to see if there are bugs we can fix and issues we can improve.
A few examples:
- Alot of people will probably see the fancy animation in Angular Material 'placeholder' on text fields transition into a floating label when it receives focus as not having much functional purpose. On mobile, given space constraints, I feel it's a real innovation, not just sugar.
- Because of the differences (and discrepancies in behavior) between the 'time' input field on both mobile web platforms I went out of my way to build an analog clock face to bring consistency between platforms and more reasonable behavior. Some of it is probably personal preference, but I think having an analog clock face is objectively better from the perspective that you can set time (at least how I designed mine) with 2 taps (and maybe one more to toggle the meridian). Compared to how iOS and Android HTML inputs work natively it may not be much of a difference in the eye of the user, but I think there is a lot of room for improvement in this space.
- "tabbing" behavior between fields on a form are different, and because of a strange design decision on Apple's part, it's impossible to reconcile. There are 2 "tabbing" arrows on the iOS keyboard which send no events to the DOM.
- I could probably go on but hopefully it paints a picture of how difficult it is to create a consistent experience easily across these platforms. Not to mention that I get the feeling the number of mobile browser / web-view options (and thus differences that may or may not be reconcilable) will just continue to grow. By decoupling the UI form input component from the native elements it will bring more consistency to the user. I don't know if Angular Material (or other material design libraries) have a goal currently to decouple from the native elements completely, but they feel like they're the furthest along in this respect.
Hi Clarity team, What would you say the primary motivation in switching from material2 or ng2-bootstrap to clarity would be? At my work we have an Angular 2 app still in development and have been rather dissatisfied with the available component libraries so far. We're at a point where it wouldn't be unreasonable to switch UI frameworks. Additionally it looks like you have only implemented some of the material design…
Hi water42, I think material2 and other frameworks are fine frameworks and are worth your consideration. We really built Clarity because we were in your position. No framework out there was able to provide us with what we needed to ship high quality, enterprise software but with modern and consumer-like UIs. We needed that framework to care deeply about user experience (not just provide code) and we wanted to make su…