Explore >> Select a destination
|
You are here 
|
doordash.engineering | ||
| | | | |
swiftwithmajid.com
|
|
| | | | | Nowadays, Apple platform development has undergone significant changes. Previously, we believed that building the core of an app around UIKit and using SwiftUI for certain screens was a good idea. This week, we'll delve into the foundation of app development using SwiftUI, while also exploring UIKit for scenarios where performance truly matters. | |
| | | | |
swiftui-lab.com
|
|
| | | | | When we double wrap SwiftUI views inside a Representables and a Hosting Views, we open the door to new possibilites of what can be achieved with SwiftUI. | |
| | | | |
swiftrocks.com
|
|
| | | | | I had played with SwiftUI before, but it wasn't until now that I had built a complete app with it. Here's my experience! | |
| | | | |
nguyenhuythanh.com
|
|
| | | In web development and deployment, most software engineers are familiar with either: Separating the built SPA and the backend (Client-Side Rendering), or Return HTML directly from the backend (Server-Side Rendering) I recently (re)discovered 1 that there is a third way: embedding the built SPA into the backend's binary file, and serving it directly. I think this is an elegant approach, as the pros are: Simpler deployment as we only have one binary file in the end Simpler code where we don't have to take into account CORS and the backend endpoint since the frontend and backend are served from the same origin 2 The cons are quite clear: | ||
