A Passionate Technologists' Journal

iOS14: App Library - Organisation of apps into a single page onto the home screen Widgets - On Home screen,   In any sizes you want Picture in Picture(PIP) - Across the system Siri: 25B requests/ month Send messages via Siri directly Supports translations Answers to common queries by browsing through the web for you Calls won’t block the whole app but come with a compact notification Translation App: Language translation Supports audio & text Supports 11 langs Messages: Memoji: More ways to style/design your memories Inline replies (Finally) Member mention in the group (Notified only when you’re mentioned) Maps: Privacy priority/matters as usual Looks like they’ve copied most of the features that google maps already has for years (Finally) Cycling/ Elevations EV routing CarPlay: 95% in the US | 80% new cars   worldwide New apps: Parking, EV Charging, Food Ordering iPhone is your car key: Digital version of Car keys (2021 BMW 5 Series) Keys can be shared with your co-driver...

Introduction: When I got to watch this WWDC video where the Apple engineers introduced a brand new Combine framework that enables developers to write asynchronous programs effectively, I was literally taken away after watching it. I will tell you the shocking story along the way. Let’s start by putting Apple’s definition for the Combine framework: “ A unified, declarative API for processing values overtime ” Combine introduces the framework’s main characteristics as: Generic Type-Safe Composition first The ‘Combine’ is Apple’s first asynchronous event-handling framework. If you’ve done reactive programming earlier, you’d be already aware but all you’ve done is only the imperative programming so far, then read this will serve as a good starting point. A generic definition of Reactive Programming goes like this: Reactive programming is an asynchronous programming paradigm oriented around data streams and the propagation of change. In th...

Introduction: If you’re looking for an introduction to SwiftUI, this serves as a good starting point. This is about my experience learning/building the first SwiftUI app, that was built while learning the SwiftUI’s layout system. I tried to build out an iPad app(Since iPhone doesn’t fit well for this app) that’d display Resume based upon the content provided to it in the intended format.  Here’s the Github repo of the open-sourced iPad app for the complete details. The entire app’s/resume’s template is based upon this resume template with just a few tweaks added to it. So, now we have the UI for the app ready that we intend to develop with SwiftUI. On top of it, I planned to have a couple of additions with respect to the requirements of the app: Theming: The entire app should be easily ‘Themable’ aka easy to configure/apply themes Icons: The app shouldn’t use any of the images and should use only the fonts so that it easily adapts to our ‘Themabl...

Introduction Let’s start with Apple’s Own Definition : “SwiftUI is an innovative, exceptionally simple way to build user interfaces across all Apple platforms with the power of Swift. Build user interfaces for any Apple device using just one set of tools and APIs. With a declarative Swift syntax that’s easy to read and natural to write, SwiftUI works seamlessly with new Xcode design tools to keep your code and design perfectly in sync. Automatic support for Dynamic Type, Dark Mode, localization, and accessibility means your first line of SwiftUI code is already the most powerful UI code you’ve ever written.” Although it is NOT a replacement for UIKit/AppKit, take it or not, UIKit/AppKit is about to die slowly just like Objective-C and SwiftUI is going to replace UIKit/Appkit in the iOS/macOS platforms.  On SwiftUI Views: “SwiftUI Views are functions of state and not a sequence of events like UIKit”, meaning the views are created based upon your data/model and ...