nice to help others

Comments

Post a Comment

Popular posts from this blog

Swift & SwiftUI Interview Prep – Senior iOS Developers

Here are some of the key questions that came up: 1. What are PassThroughSubject and CurrentValueSubject? 2. Explain Publisher and Subscriber. 3. Difference between @State and @Binding in SwiftUI. 4. What is AnyPublisher? 5. When do we use eraseToAnyPublisher? 6. What is AnyView? 7. What does the @Published property wrapper do? 8. Write a Combine pipeline to fetch data from two different network requests and output only when both complete. (💻 Live Coding Test) 9. What is a Cancellable? 10.Types of operators in Combine. 11. Usage of sink with completion. 12. Explain switchToLatest. 13. Build a 2-screen SwiftUI app (list + detail) that makes an API call using Combine only. (⏱️ 20-min Live Coding Test) 14. Difference between onReceive and onChange modifiers. 15. Coding Exercise: 👉 Given an array of strings, transform it into a new array: Input → ["a", "b", "c"] Output → ["c-0", "b-1", "a-2"] ⚡️ Requirement: Solve this using Swif...
Read more

Stop using .onAppear() for async work in SwiftUI

.onAppear { Task { await viewModel.loadData() } } The problem? SwiftUI doesn't manage that Task for you. If the view disappears, your network call keeps running in the background. Even worse, onAppear can fire multiple times in certain navigation scenarios. 🐛 There's a better way: .task() .task { await viewModel.loadData() } That's it. SwiftUI automatically cancels the task when the view disappears. No memory leaks, no unnecessary work, no manual cleanup. But it gets even better with .task(id:) Let's say you're building a user profile screen. When the userID changes, you need to reload the data: .task(id: userID) { await viewModel.loadUser(userID) } Every time userID changes, SwiftUI cancels the previous task and starts a new one automatically. No need for .onChange(), no manual task cancellation logic. Quick comparison: ❌ .onAppear - Fires on appear, no automatic cancellation, can fire multiple times ✅ .task - Fires on appear, auto-cancels on disappear ✅ .tas...
Read more

Difference Between REST and SOAP Protocols in iPhone

REST :--->   Rest stands for Representational State Transfer. It defines a set of architectural principles by which you can design Web Services that focus on a system's resources, including how resource states are addressed and transferred over HTTP by a wide range of clients written in various languages.  REST has advantages when:---> - You have a set of resources that you want to manipulate. - You want to support navigation among resources. - You need scalability. RESTful web services are tyically stateless and therefore easily scalable. - You want to improve performance by caching web service request results at some point between the service and the consumer. SOAP :--->  Soap stands for Simple Object Access Protocol. It is a simple XML-based protocol to let applications exchange information over HTTP.                        Or SOAP is a protocol for accessing a Web Service. SOAP is for ...
Read more