1. Why should React developers consider the mobile-first approach to designing their applications?
   1. Because most users are on mobile devices and it isn't worthwhile to think about larger displays.
   2. Because targeting mobile devices as the primary display for your application ensures that you can handle mobile devices and scaling up to larger devices is easier than the other way around.
   3. It doesn't make sense. You should target larger displays first and scale down your application for mobile devices.
   4. If you're using a library such as react-bootstrap, you don't even need to think about mobile-first concepts.
2. Does react-router integrate well with react-bootstrap?
   1. Yes. Although you'll want to use the react-router-bootstrap package to make sure that you can add links to the NavItem and MenuItem components.
   2. No, you should just use regular links in your react-bootstrap components.
   3. Yes, but you should consider writing your own abstractions so that all types of react-bootstrap buttons work with the Link component.

3. How would you go about rendering lists of items using react-bootstrap?
   1. Wrap a <ul> element with a <ListGroup> component from react-bootstrap.
   2. Just use a <ul> and apply Bootstrap classes to the element.
   3. Use ListGroup and ListGroupItem components from react-bootstrap.
4. Why should you create an abstraction for react-bootstrap form components?
   1. Because react-bootstrap form components are lacking in functionality.
   2. Because there are many related components that you need to use for basic inputs and creating this abstraction makes life easier.
   3. Because this is the only way to get input validation to work.