UI composition using styled-components

Setting up Styled Components is a breeze when you use Yarn! First, you’ll add the Styled Components package using the Yarn command, letting it slip right into your project like any other package.
Just a heads-up: if you’re not running Yarn with an open terminal, you might run into some unexpected hiccups, so make sure nbn is activated before diving in.
Usually, these errors only pop up the first time you run it, so after that, you should be smooth sailing.
You’ll organize your screen layout in a dedicated styles folder, kicking things off from app.tsx .
Plus, you’ll create a new file called index.ext to easily import styled components by typing snf or scn .
This setup is tailored for React Native, and don’t forget to include various React Native components.
Make sure to set up the Safe Area View as your main root component to avoid errors when you’re working with limited components..

When diving into this project, we’re keeping things simple by focusing only on the essential components and ditching anything that isn’t necessary.
Using styled components is a game changer for managing styles—no more juggling with multiple styling methods! Just a heads up, we’re skipping React Native for this go-around and sticking to what’s directly needed.
Also, instead of using React Navigation for moving between screens, we’re keeping it straightforward with USB communication.
For now, our app is all about displaying ASCII characters, so when it receives an ‘A’, you’ll see the letter A pop up, and the same goes for any other letters.
Who knows, we might explore adding a routing library in the future!.

Hey there, let’s dive into how to neatly organize your project structure with Styled Components! First off, it’s a good idea to create a separate screens folder to keep everything organized—don’t forget to use lowercase and hyphens for those names.
You can simplify things further by using an index snippet with VFC for smooth configuration.
Now, remember that components are super versatile and can accept parameters as props, just like functions do.
Speaking of props, there’s this cool concept of pull in function components worth knowing about.
And if you’re looking for a quick way to reference your components, VFC stands for Void Function Component, which is a handy shorthand! Finally, don’t overlook the importance of a styles folder to keep your styles in check and improve your screen structure.
Make sure to have comprehensive configuration settings in place, covering everything from scene to data parameters..

In this demo, we’re using text ‘A’ sized approximately 50 to make it super visible.
We’ve got two different containers coming from styled components: one for the main style and another from a subdirectory.
Just a heads up, when you’re labeling parts as SCREENS MAIN , make sure to use capital letters before the dot for screen definitions.
We’ve also set up a mirroring program that adapts to your system’s dark/light mode by switching the container’s background to white.
Plus, we cranked the font size up to 300 peaks to really showcase the style change.
Don’t forget, there’s a styles folder in the project root that’s nicely organized.
Lastly, the main screen is laid out simply with a container and text, neatly aligned using a view for a clean UI development..

So, what’s next for USB integration? In our upcoming session, we’re diving into how to add a USB-related library that’ll help Android chat with Arduino.
Now, while we could just group our functions together on one screen, it could make them less reusable.
That’s why we’re looking at a modular approach—moving those functions to their own context.
This way, we can easily pull them into other projects whenever we need them..