FluentUI-React-Native Intern Project Ideas

--- tags: native, internship --- # FluentUI-React-Native Intern Project Ideas Ideas for intern summer project. Ideally, we can pick a few and have a natural progression where learnings from one can lead into the next. ## Requirements The ideal projects have the following characteristics - [ ] Can be accomplished within the required time frame (internship is 12 weeks, but ramp-up and wrap-up should be accounted for) - [ ] Lots of opportunities to learn - [ ] Produce appealing demos - [ ] Easy to show off post internship - [ ] No devmain! ## Ideas The following ideas all exhibit the above requirements and are ordered by how excited we are by them ### react-native-web Standing up react-native-web can be thought of as an investment in an experimentation platform. It lends itself to quick development and many potential follow-ups. This includes areas ranging from perf tools and analysis to more interactive documentation. Primary Goals: - Stand up test project RNWeb in repo - Launch to code sandbox -- follow-up - Hook up perf tools, bundle analyzer -- follow-up - Host in documentation site -- follow-up Pros & Cons: - Pro: super useful - Con: do we want to do this ourselves for repo hygience - Pro: lots of fun demo potential - Con: RN-Web is harder to find documentation for, particularly webpack setup ### Npx demo workflow In lieu of an actual snack-style/expo workflow, a cli tool invokable via npx used to launch sample/test JS on multiple platforms would be useful for experimentation and bug repros. Primary Goals: - npx command to run a JS/TS file with fluent and win32 - launch test harness, bundle on the fly, transpile TS on the fly - declare version dependencies - launches prebuilt test harness with a bundle - start with: simple cases, then expand to other cases - Can we run a bundle command remotely? Pros & Cons: - Pro: would be a great follow up to standing up react-native-web - Con: remote URI handling and bundling madness could be difficult in more complex scenarios - Con: use cases aren't very clear, needs to be better scoped ### Package creation scripts As a nice to have(perhaps as an add on), an internal package creation script for standing up new cross-platform fluent controls, would be useful. This way internal developers can worry about the control logic, rather than infrastructural details. Primary Goals: - script to scaffold a new cross-platform control Pros & Cons: - Pro: well contained - Con: feels like an "if you have time"