While the Sunshine feels somewhat simple from what we've just seen, it presented its own set of challenges and setbacks during the development. It showcases the 2 main section: the first one displays the list of locations the user has added the second one is the settings tab that lets the user choose between different units to display the temperature and the wind speed. This is where you can manage some settings and also the list of locations. Tapping the menu icon on the top left corner brings the Settings Panel. It displays all the information about the current weather conditions at a glance such as:Įach card will display the temperature, and the weather conditions are reflected through the combination of an icon and a background gradient, just like the weather card on the main screen. The weather card displays the weather at a given location, here Tokyo and Perth, with the temperature conditions and metrics such as wind speed or humidity, as well as a graph displaying the position of the sun. Screenshot of Sunshine showcasing the main screen with the weather card. The main screen features the name of the location, the date, and one of the most complex SwiftUI View I built for this app: the Weather Card. The app has three main screens, each of them having a simple role yet featuring little details for a polished look: Main Screen Although challenging, I tried to stand by these principles from the prototyping phase and throughout the development of this app. What makes it unique compared to other apps was the asset I built (sun, clouds, rain), the focus on the UX, and the little animations sprinkled across the interface. My goal was to build a simple and beautiful weather app, with "home-made" assets that would animate on the screen based on the weather at a given location. Let's take a look at my first SwiftUI app, what I built, some of the challenges I faced that made me learn a lot, and why I failed to finalize this project. Thus I felt a lookback at this whole experience would be an interesting topic for a blog post. So we can call this project a failure if you want, but I'm nonetheless still pretty proud of what I ended up building! Whether it was lack of planning, too high expectations, or just the developer experience itself, the closer I was getting to finishing this project, the less confident I became about my app being worth releasing on the App Store. However, a lot of things didn't go as planned □. I had this idea of a simple yet beautiful weather app, which seemed pretty straightforward to build. While I was, and still am, just a beginner in the iOS development world, I felt that the best way to learn would be to build an app from scratch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |