Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 28 days ago

React Native, Expo Go, Nativewind.

react-native, tailwind-css
P
Thomas TS•1,130
@ttsoares
A solution to the Tech book club landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

With each solution using React Native my code is getting closer to work beyond just Web. Styling with Nativewind is harder than regular Tailwind as it imposes limitations to be accepted by mobile devices. This challenge poses a special difficulty with that double border by hovering. With Tailwind it would be trivial, but for Nativewind some hacking was needed.

What challenges did you encounter, and how did you overcome them?

To customized taleind.confg.js to be really a concentrator of definitions spawned all over the page. That is one of the main goals of this tool, to facilitate modifying stiles just be changing the rules in this file.

What specific areas of your project would you like help with?
  • The ultimate way to use <Imagebackground> tag to control how areas are filled by images.
  • How to handle SVG files in React Native without converting them to PNG.
  • The meaning of the definitions in the metro.config.js file.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•6,530
    @MarziaJalili
    Posted 27 days ago

    Wasn't React Native for mobile applications?

    🤔🤔🤔

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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub