Live data from Hacker News

Show HN: Antd – A set of high-quality React components

ant.design

21–30 of 107 posts

Re: Show HN: Antd – A set of high-quality React components

#22
post #4

Some really beautiful components like the TreeSelect in there, not trivial to build at all. That said, the first time I loaded the page sure took a long time. Kind of sad to need Webpack to create chunks just to recreate the old effect of not loading all the content for your website all at once.

Chunking would be preferable in HTTP 2

Re: Show HN: Antd – A set of high-quality React components

#23
I was playing with it, great toolkit. The overall design language is neatly done.

Is it possible to convert the remaining site pages [0] into english.

Also, the mobile friendly components [1] also look great.

[0] https://ant.design/docs/pattern/navigation

[1] https://github.com/ant-design/1x.mobile.ant.design

Re: Show HN: Antd – A set of high-quality React components

#24
I want to speak generally about new UI components, since this is the 2nd post in a week (about a new library of UI components) that reached front page (that I've seen) which are not addressing what I see as a fundamental issue that future UI libraries should address.

For mobile platforms specifically. Now on the surface you can say that UI libraries these days, more or less, will work similarly if not exactly the same across platforms. I would say for most "types" of components this will be true. But form input field behavior is different enough between mobile platforms that I'm questioning why we aren't moving quickly away from native HTML form input fields.

I totally get the argument for accessibility (probably a lot of accessibility platforms depend on these fields), but even accessibility standards such as ARIA, because of some of these inconsistencies, should be pushing toward this goal (decoupling the form input UI components from native HTML form input fields) I think.

Does anyone else here have a strong opinion one way or another as far as their experience building PWA's on mobile where they've encountered the differences between platforms (I'm specifically familiar with Android vs. iOS)? Do you find the differences to be easy to work around? I'm especially interested in feedback from folks who have required some relatively detailed behaviors, such as consistency in how input fields behave when "tabbing" to the next / previous field, or how the "input type='time'" fields behave differently in terms of when DOM events fire while setting time. Or how native keyboard behaviors / layouts are sufficiently different that you'd prefer to have a way to make the experience within your app more consistent?

Re: Show HN: Antd – A set of high-quality React components

#26

For those wondering who it comes from, https://ant.design/docs/spec/introduce#Who-are-using-Ant-Des... The first (and presumably namesake) company is Ant Financial https://www.antgroup.com , which is described as: > Ant Financial Services Group ("Ant Financial"), was officially founded in October 2014 and originated from Alipay which is the world's leading third-party payment platform founded in 2004. So basically if…

AFAIK and.design has been used heavily in alibaba for internal applications

Re: Show HN: Antd – A set of high-quality React components

#28
post #12

I was wondering if someone who is good at JS can compare this to BluePrint[1]? [1] https://github.com/palantir/blueprint

Blueprint is meant for desktop applications. For example, Electron apps. You'll notice Blueprint tries to give that desktop app feel, versus Antd, which does not.

Re: Show HN: Antd – A set of high-quality React components

#29
post #4

Some really beautiful components like the TreeSelect in there, not trivial to build at all. That said, the first time I loaded the page sure took a long time. Kind of sad to need Webpack to create chunks just to recreate the old effect of not loading all the content for your website all at once.

It's slow probably because the web server is hosted in China..
Post reply on HN