Component viabilities

[mike-engel]

Component viabilities

[streamich]

Hey, thanks for your interest!

• TouchSensor — I would call it something like TouchSupportSensor. The question is if it has to be a render-prop, if the boolean value of it does not change over time or depending on where it is rendered in the React tree, it could simply be a plain JavaScript function.
• OSOnly — similar as previous, if the value of this component does not change over time or depending where it is rendered it could be just a plain function.
• ReducedMotionSensor — this sound something that could be done by user of this lib instead.
• Control statements — I was thinking about including them, I don't think those are terribly useful but for the sake of completeness we could include those in this lib.
• Tabs and Spinner could be added to the UI section.

[mike-engel]

Thinking about TouchSupportSensor and OSOnly, I think they could be both a function and a component. I prefer HOCs when writing my React code, personally, so I could include both.

As for control statements, similar to above, I personally find them useful as HOCs for composition, but they don't need to be in this library.

Thanks! I'll start on a PR :)