In this article I will talk about:
- Problems we’re trying to solve concerning UI development
- Playground Driven Development Approach
- Gallery Application Approach
- Xcode 11 + Canvas
Identifying the problem
In order to improve UI development experience, specifically testability and maintainability, we decided to isolate UI from business/presentation logic, collect all UI representations at the same place, ensure that we don’t create UI duplications, break components down into smaller parts as they can be reused while building other elements of the app, and of course fix the biggest inconvenience which lies in the compiling part, and takes the most time.
Below I provide an overview — highlights and challenges of approaches…
The main idea of the loading/skeleton state is to provide a visual clue that content is loading and the user has to wait before the view can be filled with data.
Example animation will satisfy following criterias:
- Animates opacity.
- Starts immediately.
- Animates infinitely + uses autoreverse.
At the end we’ll get a VStack with multiple SimmerViews inside.
- First of all we need to configure an initial value. For this we create @State property and set it to our view using .opacity(opacity).
- Then we attach .transition(.opacity) modifier with opacity option to the view. …
