Beta Roadmap

[chaance]

Copied from #371 so we can close that and create individual issues for action items.

@colmtuite @benoitgrelard @jjenzz

General

• Ensure touch support is good across all primitives.
• Test all primitives rigorously with Stitches and SC, raising issues along the way.
• Complete any unfinished features (like the positioning logic for DropdownMenu raised in the design tool).

Docs

• Add UI to docs for cycling through docs versions. (Pedro)
• Add new top-level "Composition" section, mentioning forwardRef etc. (Chance)
• Add examples to relevant primitives showing how to wrap them in good consumer APIs. (Pedro)
• Add tutorial videos for each primitive. (Pedro)

New Primitives

Loosely in order of priority.

• Submenu (Andy)
• Select (Benoît)
• Menubar (Andy)
• ToggleButtonGroup (Chance)
• Toast (Jenna)
• HoverCard (Andy)
• Carousel (Jenna)
• Toolbar

[chaance]

Complete any unfinished features (like the positioning logic for DropdownMenu raised in the design tool).

@colmtuite @benoitgrelard do either of you know what specific issue this is regarding? Just wanted to make sure we are tracking it.

Are there any other unfinished features we need to consider for a beta release?

[benoitgrelard]

Yeah I believe that's to do with the fact that the menu can overflow the view now and we'd like to constrain its height (at least in some situations). I wanted to do that before xmas but didn't have time to get to it.

[DaniGuardiola]

Don't wanna be the guy who replies "+1" but...

+1

Just kidding, thanks for your work, I'll wait patiently for this :)

[acc-nicholas]

@benoitgrelard hey, my team was asking about the status of Select and when it is planned for release in some form or another. Do you have a general timeline or estimate that i can relay back to my team? Ballpark is fine.

[noahsark769]

Also interested in trying out the Select component! Happy to help with this if I can

[acc-nicholas]

@benoitgrelard Any update on Select? Its been over 6 months and i understand this one is particularly complex, but a time estimate can inform my teams plans.

[benoitgrelard]

We're in the final phases of testing, so hopefully next month 🙂

[josias-r]

@benoitgrelard Awesome! Is there any beta/alpha available that can already be tested out? 😄

[benoitgrelard]

Not yet, but we may release a candidate at some point to test out.

[kaushalyap]

@benoitgrelard @jjenzz @andy-hook @chaance @peduarte

Great library! Thank you guys! Have more components than HeadlessUI. I really like headless, accessible components.

---

Some feedback:

I wish team focus on doing implementations of components which could not be implemented using CSS, looking at current docs following components could be easily implemented with CSS

• Avatar
• Label
• AspectRatio
• Separator

See this comment from MUI to understand what I meant. You will see some components are marked as

It seems to be a UI only problem.

Some components I like to see implemented

Common :

• Drawer
• Tags / Chips
• Pagination
• DatePicker
• Skeleton
• Autocomplete
• Notification

Good to have :

• Circular Progress
• Rating
• Timeline
• Tree
• TreeSelect
• Cascader

---

Again thank you guys! keep up the good work

Update: removed skeleton

[colmtuite]

Thanks for the feedback @kaushalyap.

Our Avatar, Label, and Separator include aria features beyond CSS, so that's why we implemented them. They're relatively simple anyway, so they haven't drained much time.

Most of the components you've listed are on our radar. You could do Chip and Skeleton with CSS, if that helps. We have an example of Skeleton in our DS. Cascader and TreeSelect are a bit odd, I'd say those are the only two we won't get around to any time soon. But we'll get around to the others asap.

Thanks again for the feedback, we'll keep at it!

Note: in future, please don't @ the entire team in posts like this, it adds to their pile of notifications unnecessarily. Thanks ❤️

[kaushalyap]

You could do Chip and Skeleton with CSS

Chip also have accessibility aspect when there is an icon (ex: close)

Note: in future, please don't @ the entire team in posts like this, it adds to their pile of notifications unnecessarily.

Okay I'll keep that in mind but thanks should be given to all the members not to a single member.

Cascader and TreeSelect are a bit odd

Yes they are not frequent but cascader useful in app like Google Docs, TreeSelect also in a case of complex data intensive application.

[davemooreuws]

Great library, it would be great to have search capabilities on the radix and stitches doc sites. Algolia doc search is a good option.

[kungpaogao]

Is it possible to try out beta components? I would love to use Carousel to create something like what's on the Radix homepage!

[jjenzz]

The beta components are all at https://radix-ui.com (the project is in beta). Anything that is not there is too unstable to share atm I'm afraid.

If I recall, the Carousel on the homepage had some hardcoded features to get it working for that particular use-case so wouldn't work for everyone.

[wiesson]

I'm also super interested in the Carousel component :)

[JuanM04]

Amazing library, I love it. I've seen previews of the Select component and it looks fantastic!

Btw, do you have plans on doing a Combobox component?

[lukebennett88]

@colmtuite that's great news, I can't wait!

[hollandThomas]

Fantastic news! 🎉
I'm curious, are there any future plans to support multi-selections? That'd be dope!

[colmtuite]

Hopes, but no current plans.

[kaushalyap]

@colmtuite Why no new components after July (according to the top comment edit history)?

[colmtuite]

Because components are complex and take a long time to build.

[p6l-richard]

I worked on a Stepper component the other day and couldn't help but miss radix' style DX by symply passing a <Stepper.Next /> or <Stepper.Previous /> component to wherever I'd like them to be (similar to the Close component of the Dialog primitive).

Any plans to build something like this?

For clarification, when I say stepper component I'm talking about something like this.