React Native, Expo Go, Nativewind, clsx.

Solution retrospective
- The realization that I do not think in
<divs>
anymore but in<Views>
. - The customization of regular tags like
<Text>
to, for example,<MyText>
where the library 'clsx' manage style classes. - The use of in-line styling when the situation demanded.
- To use the help of AIs to solve specific situations without losing the understanding about what is happening.
This design stretched the use of overlapping features. The absolute positioning of entities over different screen sizes was a challenge. Also, the design itself has some inconsistencies about font sizes and that posed difficulties in the beginning until I realized that and made the corrections at the Tailwind configuration.
What specific areas of your project would you like help with?It would be nice to have a methodology to adjust the page to different window sizes in a fluid manner. In other words, to use a positioning (absolute) system that can produce transitions between screen sizes keeping a continued and harmonic flow.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Thomas TS's solution.
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord