Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ## Styling talk
- — only use inline styling when needed
- — to pass a style to element inline pass an object into the file
- — radium allows you to style react objects w/o css and offers more possibilities; it works kinda like JSX but using CSS instead of JS if that makes sense
- — another tool for this is style-component
- — people debate which one is easier to understand/use
- ## Make/customize your own create-react-app tool
- — When an application becomes complex/depends on something else create-react-app stops being useful, but you can fork create-react-app
- — after forking you can modify the react-scripts to include extra frameworks/etc
- — This does dig deep into the backend bits of react that I don’t think flatiron covered much so ?????
- — important to merge in new updates after doing this to fix vulnerabilities etc
- ## React native on android
- — talk about pros and cons of react native
- — React native lets you use JS to create native mobile apps, you can also use UI elements from website and put on mobile app with a small amount of effort
- — react native lets one dev team do both iOS, Android and Web
- — android can be more finicky when doing react native (jsx issues, animations can be off, react native is developed with ‘iOS first’ philosophy often)
- — styling android has issues, especially for tablets
- — however, react native does let you move faster, and write code once instead of twice and overall improves the developer experience
- — react native isnt meant to replace native development entirely; especially for performance and software-hardware interaction but it can do a lot
- — start with android first if you do a cross-platform react native app because you can get away with a lot more in iOS react native
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement