Inspiration
My inspiration for Park Hopper was really to give people a tool to explore local national parks pertaining to their specific desired activities or their location. It's one thing to know about the Yosemite National Park, the Everglades, or The Grand Canyon. It's another thing to visit one of these parks. Hopefully, with Park Hopper, people could start finding national parks near their area that they could explore.
What it does
Park Hopper displays data pertaining to national parks specific to a certain query made by the user. The query is done with the National Parks API.
How we built it
Park Hopper was built using Next.JS, a microframework built on React, Tailwind (a CSS library), and many other important React libraries that are open source.
Challenges we ran into
One big challenge was working with the National Parks API, which gave some troubles, specifically in the authorization. Nevertheless, we persevered!
Accomplishments that we're proud of
The design came out really, really awesome. At first, I had a hard time coming up with a look that was appealing, but the use of images from the parks themselves turned out the really put everything together in terms of design.
What we learned
I learned a lot about working with APIs, especially those connected with huge databases with sometimes inconsistent models of data. Sometimes the JSON files would have certain data, others not, making the park pages inconsistent. However, I learned to check for these inconsistences beforehand to prevent bugs.
What's next for Park Hopper
An app version of Park Hopper would be really awesome and I think that would be the direction to go in. Another update to be made is to incorporate national parks all over the world - not just the United States.
Built With
- javascript
- next.js
- tailwind
Log in or sign up for Devpost to join the conversation.