<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Satish Thakur on Medium]]></title>
        <description><![CDATA[Stories by Satish Thakur on Medium]]></description>
        <link>https://medium.com/@satish24sp?source=rss-18c588b762c1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jv1O39IpxOyR6BtYIaI9ww.jpeg</url>
            <title>Stories by Satish Thakur on Medium</title>
            <link>https://medium.com/@satish24sp?source=rss-18c588b762c1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:13:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@satish24sp/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AGENTS.md — The File Every AI-Assisted Codebase Should Have]]></title>
            <link>https://blog.stackademic.com/agents-md-the-file-every-ai-assisted-codebase-should-have-24490170e765?source=rss-18c588b762c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/24490170e765</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[Satish Thakur]]></dc:creator>
            <pubDate>Sun, 15 Mar 2026 06:16:45 GMT</pubDate>
            <atom:updated>2026-03-19T07:36:38.580Z</atom:updated>
            <content:encoded><![CDATA[<p>A practical guide to making your repository AI-friendly and maintaining clean architecture with coding agents</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sVOYnI-lI2ukJCwNxiIOxQ.png" /></figure><p>AI tools are rapidly changing how we write software.</p><p>Tools like:</p><ul><li>GitHub Copilot</li><li>Cursor</li><li>Devin</li><li>AI coding agents</li></ul><p>can now generate code, refactor modules, and even implement features automatically.</p><p>But there’s a problem.</p><p>AI doesn’t understand your <strong>codebase rules</strong>.</p><p>It doesn’t know:</p><ul><li>your architecture</li><li>your reusable components</li><li>your coding standards</li><li>your team’s workflow</li></ul><p>Without guidance, AI may generate <strong>technically correct but architecturally wrong code</strong>.</p><p>That’s why modern repositories are starting to adopt a new file:</p><p><strong>AGENTS.md</strong></p><h3>The Problem: AI Without Context</h3><p>Imagine a large iOS project with the following structure:</p><pre>App/<br>Modules/<br>Wallet/<br>Profile/<br>Core/<br>Networking/<br>Utilities/<br>UIComponents/<br>ReusableViews/</pre><p>Your architecture follows:</p><pre>View → ViewModel → Service → API</pre><p>But an AI tool generates a new feature and writes networking logic directly inside a ViewController.</p><p>Suddenly you get:</p><pre>WalletViewController<br> ├── API call<br> ├── parsing logic<br> ├── UI code</pre><p>Now your <strong>MVVM architecture is broken</strong>.</p><p>This happens because the AI didn’t know your architecture rules.</p><h3>What is AGENTS.md?</h3><p>AGENTS.md is a <strong>repository instruction file for AI coding agents and developers</strong>.</p><p>It defines how code should be:</p><ul><li>structured</li><li>written</li><li>updated</li><li>reviewed</li></ul><p>Think of it like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J0EMahE17k_2dCQqOIJB2w.png" /></figure><p>It acts as a <strong>development playbook for humans and AI tools</strong>.</p><h3>Why AGENTS.md is Becoming Important</h3><p>As AI coding tools become common, repositories need a way to guide them.</p><p>AGENTS.md helps enforce:</p><p>✔ architecture consistency<br>✔ reusable components<br>✔ coding standards<br>✔ documentation requirements<br>✔ collaboration guidelines</p><p>Without it, large codebases become chaotic.</p><h3>Example Problem Without AGENTS.md</h3><p>You already have a reusable button component:</p><pre>UIComponents/<br>PrimaryButton.swift</pre><p>But an AI tool creates:</p><pre>RoundedButton.swift<br>ActionButton.swift<br>CustomCTAButton.swift</pre><p>Now you have <strong>four different buttons doing the same thing</strong>.</p><p>This leads to:</p><ul><li>UI inconsistency</li><li>duplicated logic</li><li>harder maintenance</li></ul><p>A simple rule inside AGENTS.md can prevent this:</p><blockquote><em>Always check for existing reusable components before creating new UI elements.</em></blockquote><h3>What a Good AGENTS.md Should Include</h3><p>A strong AGENTS.md typically includes several sections.</p><h4>1. Architecture Rules</h4><p>Define the architecture clearly.</p><p>Example for iOS:</p><pre>Architecture: MVVM + Coordinator<br>View → ViewModel → Service → API</pre><p>Rules might include:</p><ul><li>Views should contain UI logic only</li><li>ViewModels contain business logic</li><li>Networking belongs in Services</li></ul><p>This ensures generated code <strong>follows the architecture</strong>.</p><h4>2. Reusable Component Policy</h4><p>Encourage reuse instead of duplication.</p><p>Example rule:</p><pre>Before creating new UI components,<br>search the repository for existing reusable views.</pre><p>Typical reusable folders:</p><pre>UIComponents/<br>ReusableViews/<br>DesignSystem/</pre><h4>3. Coding Standards</h4><p>Define language best practices.</p><p>Example Swift rules:</p><ul><li>Avoid force unwrap (!)</li><li>Prefer struct over class</li><li>Use protocol-oriented programming</li><li>Keep functions small and readable</li></ul><p>Example:</p><pre>protocol WalletServiceProtocol {<br>    func fetchBalance() async throws -&gt; Balance<br>}</pre><h4>4. Documentation Requirements</h4><p>Large codebases require documentation.</p><p>Example:</p><pre>/// Fetch wallet balance from API<br>///<br>/// - Parameters:<br>///   - userId: Unique identifier<br>///<br>/// - Returns: Wallet balance model<br>func fetchWalletBalance(for userId: String) async throws -&gt; Balance</pre><p>This helps:</p><ul><li>new developers</li><li>code reviewers</li><li>AI agents understand the code.</li></ul><h4>5. Code Update Markers</h4><p>When updating shared code, marking changes is useful.</p><p>Example:</p><pre>// MARK: - UPDATED by Satish on 2026-03-15</pre><p>This helps reviewers quickly identify what changed.</p><h4>6. Git Workflow</h4><p>Define branching rules.</p><p>Example:</p><pre>main → production<br>develop → development<br>feature/* → new features<br>fix/* → bug fixes</pre><p>This ensures a consistent workflow across teams.</p><h3>How to Add AGENTS.md to Your Repository</h3><p>Adding this file is simple.</p><h4>Step 1</h4><p>Open your GitHub repository.</p><h4>Step 2</h4><p>Click:</p><pre>Add File → Create new file</pre><h4>Step 3</h4><p>Name the file:</p><pre>AGENTS.md</pre><h3>Step 4</h3><p>Add your coding guidelines.</p><h3>Step 5</h3><p>Commit the file.</p><p>Example commit:</p><pre>docs: add AGENTS.md for AI coding agents</pre><p>Your repository is now <strong>AI-ready</strong>.</p><h3>Basic AGENTS.md Template</h3><p>Here’s a simple template you can start with.</p><pre># AGENTS.md<br><br>## Purpose<br>Defines development rules for developers and AI agents.<br><br>## Architecture<br>MVVM + Coordinator<br>View → ViewModel → Service → API<br><br>## Reusable Components<br>Check existing components before creating new ones.<br><br>## Coding Rules<br>Avoid force unwrap<br>Prefer struct over class<br><br>## Documentation<br>Public functions must include Swift documentation.<br><br>## Code Updates<br>Mark updates using:<br>// MARK: - UPDATED by &lt;Developer&gt; on &lt;Date&gt;<br><br>## Git Workflow<br>feature/*<br>fix/*<br>main</pre><h3>Why This File Will Become Standard</h3><p>As AI-assisted development grows, repositories will increasingly require <strong>clear guidelines for automation tools</strong>.</p><p>AGENTS.md helps maintain:</p><ul><li>architecture integrity</li><li>code quality</li><li>team collaboration</li><li>AI reliability</li></ul><p>It’s a <strong>small file that protects your codebase from chaos</strong>.</p><h3>Final Thoughts</h3><p>AI tools are powerful, but they need context.</p><p>Adding an AGENTS.md file ensures that:</p><ul><li>developers</li><li>contributors</li><li>AI coding agents</li></ul><p>all follow the same development standards.</p><p>If your repository uses AI tools or has multiple contributors, consider adding AGENTS.md.</p><p>It might soon become <strong>as important as README.md</strong>.</p><h3>Author</h3><p><a href="https://satish24sp.github.io/">Satish</a><br>Senior iOS Engineer<br>Swift | UIKit | SwiftUI</p><p>Building scalable iOS applications used by millions of users.</p><p>Follow me on:<br>🔗 <a href="https://www.linkedin.com/in/satish-iosdev/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24490170e765" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/agents-md-the-file-every-ai-assisted-codebase-should-have-24490170e765">AGENTS.md — The File Every AI-Assisted Codebase Should Have</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CocoaPods Is Entering Read-Only Mode — And That’s a Good Thing for iOS]]></title>
            <link>https://blog.stackademic.com/cocoapods-is-entering-read-only-mode-and-thats-a-good-thing-for-ios-3a655b7293c5?source=rss-18c588b762c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a655b7293c5</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[cocoapods]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Satish Thakur]]></dc:creator>
            <pubDate>Thu, 29 Jan 2026 17:32:40 GMT</pubDate>
            <atom:updated>2026-01-29T20:06:30.323Z</atom:updated>
            <content:encoded><![CDATA[<h3>CocoaPods Is Entering Read-Only Mode — And That’s a Good Thing for iOS</h3><p>Technology evolves. So do the tools we rely on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jK7sYhaEQPX3XIfqDDIdkQ.png" /></figure><p>For more than a decade, <strong>CocoaPods</strong> has been the backbone of the iOS dependency ecosystem. It helped scale entire generations of apps, teams, and startups. It made modular code practical long before Swift Package Manager even existed.</p><p>But ecosystems don’t stand still.</p><p>On <strong>December 2, 2026</strong>, CocoaPods will officially become <strong>read-only</strong>.<br>After years in maintenance mode, <strong>Trunk will be permanently locked</strong>.</p><p>This is not the end of iOS open source.<br>It’s the beginning of a cleaner, more modern chapter.</p><p><em>📌 Check more about </em><a href="https://medium.com/@satish24sp/understanding-the-difference-between-spm-frameworks-cocoapods-and-build-plug-ins-in-swift-1940eb103ae5"><em>SPM, Framework, CocoaPods and Build Plug-ins</em></a><em>.</em></p><h3>What “Read-Only” Actually Means</h3><p>When CocoaPods enters read-only mode:</p><ul><li>❌ No new pods can be published</li><li>❌ No existing pods can be updated</li><li>❌ trunk push will be blocked</li><li>✅ Existing pods will continue to resolve</li></ul><p>In other words, CocoaPods won’t suddenly break your app — but it will <strong>stop evolving</strong>.</p><p>This is a sunset, not a shutdown.</p><h3>The Official Timeline</h3><p>The CocoaPods team has been preparing the ecosystem for this moment:</p><ul><li><strong>January 2025</strong> — Initial notices</li><li><strong>September–October 2026</strong> — Final reminders</li><li><strong>November 2026</strong> — Dry run of Trunk lock</li><li><strong>December 2, 2026</strong> — Trunk permanently locked</li></ul><p>This isn’t abrupt. It’s deliberate.</p><h3>Why This Is Happening</h3><p>The short answer: <strong>Swift Package Manager won.</strong></p><p>What started as a basic tool for Swift-only projects has matured into a full ecosystem standard:</p><ul><li>Built directly into Xcode</li><li>Faster and more reliable</li><li>No external tooling required</li><li>Native to Swift-first development</li><li>Better CI/CD integration</li><li>Easier onboarding for new developers</li></ul><p>SPM is no longer “the future.”<br>It is the <strong>present</strong>.</p><h3>This Is Not a Failure — It’s a Handoff</h3><p>CocoaPods did not lose.<br>It <strong>completed its mission</strong>.</p><p>It solved a real problem at a critical time in iOS history:</p><ul><li>When Swift was new</li><li>When binary frameworks were fragile</li><li>When dependency management was painful</li></ul><p>CocoaPods moved the entire community forward.</p><p>Now, the baton has been passed.</p><p>Great tools don’t need to last forever.<br>They need to <strong>change the industry</strong>.</p><p>CocoaPods did exactly that.</p><h3>What About Carthage?</h3><p>Carthage still makes sense <em>in specific scenarios</em>:</p><ul><li>Heavy reliance on binary frameworks</li><li>Maximum control over build artifacts</li><li>Maintaining legacy projects</li></ul><p>But for <strong>new development</strong>?</p><p>Swift Package Manager is the safest long-term bet.</p><h3>Simple Takeaway</h3><p><em>CocoaPods → Retiring (read-only)</em></p><p><em>Carthage → Surviving, but niche</em></p><p><em>SPM → The future standard</em></p><h3>Migration Guidance (2025–2026)</h3><ul><li><strong>CocoaPods → Migrate to SPM first</strong></li><li><strong>Carthage → Evaluate, then migrate when possible</strong></li></ul><p>The earlier you migrate, the less technical debt you carry forward.</p><h3>Final Thought</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VaA3b9NxcGIamQPU1KUw-w.png" /></figure><p>CocoaPods isn’t fading away — it’s stepping aside.</p><p>It carried the iOS ecosystem through one of its most important growth phases, when Swift was young, modularity was painful, and dependency management was a real barrier to scale. Thousands of companies, millions of apps, and an entire generation of developers built on top of it.</p><p>Now, the platform has matured.</p><p>Swift Package Manager represents a simpler, faster, more native future — and CocoaPods is making room for that future with grace.</p><p>This transition is not about replacement.<br>It’s about <strong>evolution</strong>.</p><p>So as we migrate forward, we’re not just changing tools — <br>we’re honoring the one that made this era possible.</p><p><strong>Thank you, CocoaPods. You moved iOS forward.</strong> 👏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a655b7293c5" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/cocoapods-is-entering-read-only-mode-and-thats-a-good-thing-for-ios-3a655b7293c5">CocoaPods Is Entering Read-Only Mode — And That’s a Good Thing for iOS</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Disable or Opt-Out Liquid Glass in SwiftUI and UIKit | iOS 26]]></title>
            <link>https://blog.stackademic.com/disable-or-opt-out-liquid-glass-in-swiftui-and-uikit-ios-26-5c6d55d3e8e5?source=rss-18c588b762c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c6d55d3e8e5</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[liquid-glass]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Satish Thakur]]></dc:creator>
            <pubDate>Sat, 03 Jan 2026 14:51:51 GMT</pubDate>
            <atom:updated>2026-01-17T08:36:55.094Z</atom:updated>
            <content:encoded><![CDATA[<p>WWDC 2025 introduced us to <strong>Liquid Glass</strong>, the most significant visual overhaul since iOS 7. While the fluid, lensing, and depth-aware effects look stunning in Apple’s native apps, they can be a nightmare for existing apps with custom UI logic.</p><p>Here’s the uncomfortable truth:</p><blockquote><strong><em>Liquid Glass looks amazing in marketing screens — and breaks real production apps.</em></strong></blockquote><p>If your app:</p><ul><li>Is text-heavy</li><li>Was designed with solid surfaces</li><li>Prioritizes readability and contrast</li><li>Serves enterprise or accessibility-focused users</li></ul><p>…you’ve probably already noticed the problems.</p><p><strong><em>This post is not about hating Liquid Glass.<br>It’s about surviving it until Apple gives us a proper opt-out or you switch to Brilliant Liquid Glass Feature.</em></strong></p><p>Until you can fully refactor your UI for this new spatial language, here are the temporary workarounds to regain control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*858A6WY8PmZx-qi1uNoCcA.png" /></figure><h3>1. The Global “Escape Hatch” (Info.plist)</h3><p>If your app is completely broken by the new design system (e.g., your custom UITableView headers are overlapping or the Tab View is unreadable), Apple provides a temporary global opt-out.</p><p><strong>Add this key to your </strong><strong>Info.plist:</strong></p><ul><li><strong>Key:</strong> UIDesignRequiresCompatibility</li><li><strong>Value:</strong> YES (Boolean)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e10GIcRbANyYWIwzg93Fzg.png" /><figcaption>info.plist</figcaption></figure><blockquote>That’s it.</blockquote><blockquote>No code.<br>No view-level overrides.<br>No fighting system materials.</blockquote><p><strong>But please note</strong></p><blockquote><em>This is a </em><strong><em>temporary</em></strong><em> measure. Apple typically deprecates compatibility flags within one major release cycle (expected to be removed in iOS 27 as per </em>Multiple reputable developer sources (blogs, community posts, and videos referencing Apple<em>). So please use it wisely because t</em>his is not a feature. It is a <strong>grace period</strong>.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6f9khm1ToeXboyFRx-rj9g.png" /><figcaption>You can check this in the Apple <a href="https://developer.apple.com/documentation/BundleResources/Information-Property-List/UIDesignRequiresCompatibility">documentation</a>.</figcaption></figure><h3>2. Global Control (Single Point Entry)</h3><p>To manage the transition without the plist, you can set “flat” defaults at the entry point of your app.</p><h4>UIKit: AppDelegate / SceneDelegate</h4><p>Configure the appearance proxy at launch to strip glass effects from all container and navigation components.</p><pre>func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -&gt; Bool {<br>    <br>    // 1. Disable lensing/morphing in all ScrollViews, TableViews, &amp; CollectionViews<br>    UIScrollView.appearance().allowsLiquidTransform = false<br>    <br>    // 2. Navigation Bar Fix<br>    let navAppearance = UINavigationBarAppearance()<br>    navAppearance.configureWithOpaqueBackground()<br>    UINavigationBar.appearance().standardAppearance = navAppearance<br>    UINavigationBar.appearance().scrollEdgeAppearance = navAppearance<br>    <br>    // 3. Tab Bar Fix (Floating Capsule Fix)<br>    let tabAppearance = UITabBarAppearance()<br>    tabAppearance.configureWithOpaqueBackground() <br>    UITabBar.appearance().standardAppearance = tabAppearance<br>    if #available(iOS 26.0, *) {<br>        UITabBar.appearance().scrollEdgeAppearance = tabAppearance<br>    }<br>    return true<br>}</pre><h4>SwiftUI: Root Level Environment</h4><p>Wrap your main view hierarchy to disable glass rendering for the entire app.</p><pre>@main<br>struct MyApp: App {<br>    var body: some Scene {<br>        WindowGroup {<br>            ContentView()<br>                .environment(\.glassRenderingMode, .disabled) <br>        }<br>    }<br>}</pre><h3>3. Component-Specific Overrides (The Surgical Approach)</h3><p>If you want to keep Liquid Glass in some areas but disable it for others, use these targeted snippets.</p><h4><strong>SwiftUI Workarounds</strong></h4><h4><strong>1. Avoid System Materials Explicitly</strong></h4><p><strong>❌ Causes Liquid Glass</strong></p><pre>.background(.ultraThinMaterial)</pre><p><strong>✅ Replace with Solid Colors</strong></p><pre>.background(Color(.systemBackground))</pre><p>or</p><pre>.background(Color.white)</pre><h4>2. Disable Transparency at the View Level</h4><p>Use <strong>opaque backgrounds</strong> to block refraction:</p><pre>VStack {<br>    Text(&quot;Hello&quot;)<br>        .foregroundColor(.black)<br>}<br>.background(<br>    Color.white<br>        .opacity(1.0)<br>)</pre><p>💡 Even opacity(0.99) can re-enable glass effects — use 1.0.</p><h4>3. Buttons Without Liquid Glass</h4><p><strong>❌ Default Button Style (may inherit glass)</strong></p><pre>Button(&quot;Submit&quot;) {<br>    // action<br>}</pre><p><strong>✅ Use a Plain Button Style</strong></p><pre>Button(&quot;Submit&quot;) {<br>    // action<br>}<br>.buttonStyle(.plain)<br>.background(Color.blue)<br>.foregroundColor(.white)<br>.cornerRadius(8)</pre><p><strong>4. Text &amp; Label Clarity Fix</strong></p><p>Force text to render on opaque layers:</p><pre>Text(&quot;Important Text&quot;)<br>    .padding()<br>    .background(Color.white)<br>    .foregroundColor(.black)</pre><p><strong>5. ScrollView Without Glass Background</strong></p><pre>ScrollView {<br>    VStack {<br>        Text(&quot;Content&quot;)<br>    }<br>}<br>.scrollContentBackground(.hidden)<br>.background(Color(.systemBackground))</pre><p><strong>6. List Without Liquid Glass</strong></p><pre>List {<br>    Text(&quot;Row 1&quot;)<br>    Text(&quot;Row 2&quot;)<br>}<br>.listStyle(.plain)<br>.scrollContentBackground(.hidden)<br>.background(Color.white)</pre><h4>UIKit Workarounds</h4><p>UIKit gives more control — but also requires more manual cleanup.</p><p><strong>1. Remove UIVisualEffectView</strong></p><p>Liquid Glass heavily relies on UIVisualEffectView.</p><pre>view.subviews<br>    .compactMap { $0 as? UIVisualEffectView }<br>    .forEach { $0.removeFromSuperview() }</pre><p>⚠️ Be cautious — removing system views may affect layout.</p><p><strong>2. Force Opaque Backgrounds</strong></p><pre>view.backgroundColor = .systemBackground<br>view.isOpaque = true</pre><p>For labels:</p><pre>label.backgroundColor = .white<br>label.isOpaque = true</pre><p><strong>3. UIButton Without Glass</strong></p><pre>let button = UIButton(type: .system)<br>button.setTitle(&quot;Submit&quot;, for: .normal)<br>button.backgroundColor = .systemBlue<br>button.setTitleColor(.white, for: .normal)<br>button.layer.cornerRadius = 8</pre><p>Avoid:</p><pre>UIButton.Configuration.filled()</pre><p><strong>4. UITableView Without Liquid Glass</strong></p><pre>tableView.backgroundColor = .white<br>tableView.backgroundView = UIView()<br>tableView.isOpaque = true</pre><p>Also:</p><pre>tableView.separatorEffect = nil</pre><p><strong>5. UICollectionView Fix</strong></p><pre>collectionView.backgroundColor = .white<br>collectionView.isOpaque = true</pre><p>Cell:</p><pre>cell.contentView.backgroundColor = .white<br>cell.contentView.isOpaque = true</pre><p><strong>6. Disable Blur Effects Globally (Last Resort)</strong></p><pre>UIAccessibility.isReduceTransparencyEnabled = true</pre><p>⚠️ This is <strong>not App Store-safe</strong> if forced without user intent.<br>Only respect it if <strong>user enables Reduce Transparency</strong>.</p><h3>Conclusion</h3><h4>Temporary Relief, Not a Permanent Solution</h4><p>Liquid Glass is a beautiful evolution, but it isn’t functional for every use case.</p><p>While disabling or opting out of <strong>Liquid Glass</strong> might be necessary to preserve your app’s current branding or fix immediate legibility bugs, it is important to view these workarounds as temporary measures.</p><p>By using a combination of Environment keys and UIAppearance, you can ensure your app remains usable while you plan for a permanent design update.</p><p>Use these fixes to keep your app functional today, but start experimenting with how your brand can live <em>within</em> the glass in the future.</p><p><strong>But</strong></p><p>As we move deeper into the <strong>Apple OS 26</strong> lifecycle, Apple is increasingly optimizing the kernel and GPU specifically for these refractive, spatial materials. Relying on legacy overrides like .none or UIBlurEffect.classic may eventually lead to:</p><ul><li><strong>Performance Degradation:</strong> Future versions of iOS and macOS will prioritize the Liquid Glass rendering pipeline; older materials may lose hardware acceleration.</li><li><strong>Visual Inconsistency:</strong> As users grow accustomed to the depth and “fluidity” of the native OS, apps that strictly opt-out will begin to feel dated or “broken” in the context of the modern UI.</li><li><strong>Future Deprecation:</strong> History shows that Apple eventually removes support for legacy UI materials. There will likely come a point where above opt-outs flags simply no longer work.</li></ul><h4>🚀 Don’t Wait Until It’s Too Late</h4><p>It is strongly recommend using the time gained by these “opt-out” methods to <strong>re-design and iterate</strong>. Start by incrementally adopting Liquid Glass in non-critical areas, such as floating action buttons or secondary menus.</p><p><strong>The goal is clear:</strong> Transition your app to the Liquid Glass standard now to ensure your interface remains premium, accessible, and fully integrated with the next generation of Apple hardware.</p><p>Don’t let your app get left behind in a static, glassless past — <strong>upgrade to the liquid future today.</strong></p><p><strong>Here are the official links shared by Apple for us:</strong></p><ol><li><a href="https://developer.apple.com/design/?cid=ht-new-design-g-l-2">Explore the new design</a></li><li><a href="https://developer.apple.com/design/new-design-gallery/?cid=ht-new-design-g-l">Browse Examples</a></li></ol><h4><strong>Happy Coding!</strong></h4><p>If you found value in this article, consider</p><p>👍 Clapping &amp; leaving feedback</p><p>💬 Sharing it with your team or</p><p>🔖 Bookmarking it for future reference.</p><h3>Thanks for reading! ❤</h3><p>Follow me on:<br>🔗 <a href="https://www.linkedin.com/in/satish-iosdev/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c6d55d3e8e5" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/disable-or-opt-out-liquid-glass-in-swiftui-and-uikit-ios-26-5c6d55d3e8e5">Disable or Opt-Out Liquid Glass in SwiftUI and UIKit | iOS 26</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding the Difference Between SPM, Frameworks, CocoaPods, and Build Plug-ins in Swift]]></title>
            <link>https://medium.com/@satish24sp/understanding-the-difference-between-spm-frameworks-cocoapods-and-build-plug-ins-in-swift-1940eb103ae5?source=rss-18c588b762c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/1940eb103ae5</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[iphone]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Satish Thakur]]></dc:creator>
            <pubDate>Sat, 06 Dec 2025 10:18:09 GMT</pubDate>
            <atom:updated>2025-12-06T10:18:09.040Z</atom:updated>
            <content:encoded><![CDATA[<p>When building modern iOS and macOS applications, managing dependencies and modularizing code are essential for scalability and maintainability.</p><p>Swift developers today have a variety of tools and formats to structure their code:</p><ul><li><strong>Swift Package Manager (SPM)</strong></li><li><strong>Frameworks (Static, Dynamic, XCFrameworks)</strong></li><li><strong>CocoaPods</strong></li><li><strong>Xcode/Swift Plug-ins (Build Tool Plug-ins &amp; Command Plug-ins)</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YdCUog64ka9P1Fvq-iC4jw.png" /></figure><p>Each serves a different purpose, comes with its own strengths, and is suitable for different stages of development.</p><p>In this article, we’ll break down the differences between these tools, discuss when to use each, and look at code examples and practical advice for choosing the right approach.</p><h3>🔹 Swift Package Manager (SPM)</h3><h3>🔸 What is SPM?</h3><p>Swift Package Manager is Apple’s official package manager integrated directly into Swift and Xcode.</p><p>It allows you to define and manage dependencies using a simple Package.swift file.</p><p>SPM has become the default choice for many modern Swift libraries because it is fast, native, and requires no external installation.</p><h3>🔸 Types of SPM Components</h3><h4>1. Libraries</h4><ul><li>Static or dynamic</li><li>Produced with .library in Package.swift</li></ul><h4>2. Executables</h4><ul><li>CLI tools bundled within a package</li></ul><h4>3. Targets</h4><ul><li>target → main module</li><li>testTarget → tests</li><li>binaryTarget → XCFramework or binary blob</li></ul><h4>4. Plug-ins</h4><ul><li>Build Tool Plug-ins</li><li>Command Plug-ins</li></ul><h3>🔸 How it Works</h3><p>You define a package using a manifest file:</p><pre>// Package.swift<br>// swift-tools-version: 5.9<br>import PackageDescription<br><br>let package = Package(<br>    name: &quot;MyLibrary&quot;,<br>    platforms: [.iOS(.v15)],<br>    products: [<br>        .library(name: &quot;MyLibrary&quot;, targets: [&quot;MyLibrary&quot;])<br>    ],<br>    dependencies: [],<br>    targets: [<br>        .target(name: &quot;MyLibrary&quot;, dependencies: []),<br>        .testTarget(name: &quot;MyLibraryTests&quot;, dependencies: [&quot;MyLibrary&quot;])<br>    ]<br>)</pre><h3>🔸 Pros</h3><ul><li>⚙️ Native to Xcode</li><li>🚀 Built into Xcode and Swift</li><li>💨 Fast, minimal setup</li><li>🧩 Great for modularization</li><li>🧲 Git-based versioning</li><li>🔐 Works across Apple platforms</li></ul><h3>🔸 Cons</h3><ul><li>Limited support for resource-heavy libraries (compared to Pods)</li><li>No built-in support for script phases or complex config</li><li>Some legacy libraries still not migrated</li></ul><h3>🔸 Best For</h3><ul><li>New projects</li><li>Modular codebases</li><li>Reusable Swift libraries and SDKs</li></ul><h3>🔹 Frameworks</h3><h3>🔸 What is a Framework?</h3><p>A framework is a compiled bundle of code and resources. You can build your code as a <strong>static</strong> or <strong>dynamic</strong> framework and embed it directly into your app.</p><p>Frameworks are the traditional way to reuse code across multiple projects before package managers became popular.</p><h3>🔸 Types of Frameworks</h3><h4>1. Static Frameworks</h4><ul><li>Compiled directly into app binary</li><li>Faster runtime, smaller footprint</li></ul><h4>2. Dynamic Frameworks</h4><ul><li>Loaded at runtime</li><li>Good for modularity but slower startup</li></ul><h4>3. XCFrameworks</h4><ul><li>Multi-platform archive (iOS, macOS, Simulator)</li><li>Now standard for binary SDK distribution</li></ul><h4>Example: Creating a Framework</h4><ol><li>In Xcode: File → New → Project → Framework</li><li>Add your reusable code</li><li>Export .xcframework for distribution</li></ol><h3>🔸 Pros</h3><ul><li>📦 Encapsulates compiled and stable code</li><li>🧵 Can include resources, assets, core data models</li><li>🔧 Useful for closed-source SDK distribution</li><li>🧰 Compatible everywhere (SPM, Pods)</li></ul><h3>🔸 Cons</h3><ul><li>Requires manual version management</li><li>Not ideal for rapidly changing code</li><li>Harder to integrate compared to SPM</li></ul><h3>🔸 Best For</h3><ul><li>Enterprise SDK distribution</li><li>Closed-source or binary only libraries</li><li>Legacy projects</li><li>When distributing to outside teams</li></ul><h3>🔹 CocoaPods</h3><h3>🔸 What are CocoaPods?</h3><p>CocoaPods was the dominant dependency manager before SPM became official. It uses a Podfile to integrate external libraries into an Xcode workspace.</p><h3>🔸 Types of Pods</h3><h4>1. Standard Pods (public)</h4><p>Available on the public Spec Repo.</p><h4>2. Private Pods</h4><p>Useful for enterprise internal libraries.</p><h4>3. Pods with Resources</h4><ul><li>Fonts</li><li>Images</li><li>Storyboards</li><li>JSON/XML files</li></ul><h4>4. Pods with Script Phases</h4><p>Used for advanced integrations like Firebase.</p><h4>Example Podfile</h4><pre>platform :ios, &#39;15.0&#39;<br>target &#39;MyApp&#39; do<br>  use_frameworks!<br>  pod &#39;Alamofire&#39;<br>  pod &#39;SnapKit&#39;<br>end</pre><p>Then:</p><pre>pod install</pre><h3>🔸 Pros</h3><ul><li>🛠️ Mature ecosystem, thousands of libraries</li><li>📁 Excellent support for resources</li><li>🔗 Supports static and dynamic frameworks</li></ul><h3>🔸 Cons</h3><ul><li>Slower builds</li><li>Requires external tool installation</li><li>Generates .xcworkspace which some devs dislike</li><li>Many modern libraries are moving to SPM</li></ul><h3>🔸 Best For</h3><ul><li>Legacy apps already using Pods</li><li>Libraries not available in SPM</li><li>Apps needing large resource-heavy UI SDKs</li></ul><h3>🔹 Xcode Build Plug-ins</h3><h3>🔸 What are Build Plug-ins?</h3><p>Introduced in Swift 5.6, <strong>Xcode Build Plug-ins</strong> extend SPM by running custom scripts during the build process — such as code generation, asset processing, or linting.</p><p>Xcode Plug-ins extend SPM and replace custom build scripts.</p><h3>🔸 Types of Build Plug-ins</h3><h4>1. Build Tool Plug-ins</h4><p>Runs automatically <strong>during the build process</strong>.</p><p><strong>Used For:</strong></p><ul><li>Code generation (Sourcery, Protobuf)</li><li>Linting (SwiftLint)</li><li>Asset processing</li></ul><pre>.plugin(<br>  name: &quot;SwiftLintPlugin&quot;,<br>  capability: .buildTool(),<br>  dependencies: [.target(name: &quot;SwiftLintBinary&quot;)]<br>)</pre><h4>2. Command Plug-ins</h4><p>Triggered manually from the Xcode menu.</p><p><strong>Used For:</strong></p><ul><li>Creating file templates</li><li>Running formatting commands</li><li>Utility automation</li></ul><p><strong>Example:</strong></p><pre>.plugin(<br>  name: &quot;GenerateTemplates&quot;,<br>  capability: .command(<br>    intent: .sourceCodeFormatting(),<br>    permissions: [.writeToPackageDirectory]<br>  )<br>)</pre><h3>🔸 Pros</h3><ul><li>⚙️ Automate repetitive tasks</li><li>🔌 Native Xcode integration</li><li>🚫 Eliminates the need for ugly shell scripts</li></ul><h3>🔸 Cons</h3><ul><li>Still new → limited ecosystem</li><li>Only works with SPM packages</li><li>Cannot modify core build settings</li></ul><h3>🔸 Best For</h3><ul><li>Teams wanting automation</li><li>Projects using SPM heavily</li><li>Code generation workflows</li></ul><h3>📊 Summary Table</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uIRIcGq7A9A7s0Ld5kDUog.png" /></figure><h3>🧭 When to Choose What?</h3><ul><li>Use <strong>SPM</strong> for modern, clean, fast dependency setup Swift apps.</li><li>Use <strong>Frameworks/XCFrameworks</strong> for binary and closed-source distribution or SDKs.</li><li>Use <strong>CocoaPods</strong> only when necessary for legacy libraries that are not migrated to SPM.</li><li>Use <strong>Xcode Plug-ins</strong> for automation and code generation or custom build logic built directly into SPM.</li></ul><h3>🎯 Final Thoughts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7JJlupvxZgXND4wSXuA19A.png" /></figure><p>SPM, Frameworks, CocoaPods, and Build Plug-ins are not competitors — they solve different problems.</p><p>Modern Swift development leans toward <strong>SPM + Build Plug-ins</strong>, but frameworks and CocoaPods still have important use cases.</p><p>Understanding how they differ empowers you to build cleaner, modular, and scalable Swift apps.</p><p>If you found value in this article, consider</p><p>👍 Clapping &amp; leaving feedback</p><p>💬 Sharing it with your team or</p><p>🔖 Bookmarking it for future reference.</p><h3>Thanks for reading! ❤</h3><p>Follow me on:<br>🔗 <a href="https://www.linkedin.com/in/satish-iosdev/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1940eb103ae5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WWDC 2025 Recap: Apple Intelligence, iOS 26, Xcode 26, Swift 6 & The Liquid Glass Era]]></title>
            <link>https://medium.com/@satish24sp/wwdc-2025-recap-apple-intelligence-ios-26-xcode-26-swift-6-the-liquid-glass-era-a8134391abad?source=rss-18c588b762c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8134391abad</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[wwdc-2025]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[wwdc]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Satish Thakur]]></dc:creator>
            <pubDate>Sun, 22 Jun 2025 03:52:35 GMT</pubDate>
            <atom:updated>2025-06-22T04:10:37.129Z</atom:updated>
            <content:encoded><![CDATA[<p>Apple’s WWDC 2025 keynote wasn’t just about incremental updates — it marked a bold shift in design, AI integration, and developer tooling across the entire Apple ecosystem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WsWd4MZdSBfzVMHJrZGShw.png" /></figure><p>From the futuristic <strong>Liquid Glass UI</strong> to <strong>on-device AI models</strong>, and the most intelligent version of Xcode yet, here’s a crisp summary of everything you need to know.</p><blockquote><em>💡 This isn’t just a visual overhaul — it’s a complete platform rethink.</em></blockquote><h3>🔄 Unified OS Versioning or Year-Based OS Naming:</h3><p>Apple has aligned its platforms under a new <strong>year-based naming scheme</strong>, simplifying version tracking:</p><ul><li>iOS 19 → <strong>iOS 26</strong></li><li>iPadOS 19 → <strong>iPadOS 26</strong></li><li>macOS Sequoia → <strong>macOS 26 (Tahoe)</strong></li><li>watchOS 11 → <strong>watchOS 26</strong></li><li>tvOS 19 → <strong>tvOS 26</strong></li><li>visionOS → <strong>visionOS 26</strong></li></ul><p>This change makes cross-platform development cleaner, improve version clarity and sets the stage for future convergence. This simplifies developer targeting and product alignment.</p><h3>🧊 Liquid Glass Design: The New UI Language</h3><p>The biggest visual refresh in over a decade, <strong>Liquid Glass</strong>, brings a modern, translucent aesthetic to all Apple platforms.</p><ul><li>Dynamic, layered interfaces</li><li>Frosted backgrounds with depth effects</li><li>Real-time color adaptation from system themes and content</li></ul><p><a href="https://www.apple.com/in/newsroom/2025/06/apple-introduces-a-delightful-and-elegant-new-software-design/?videoid=c6256ec6b063b61342e3bb1f004919e1">https://www.apple.com/in/newsroom/2025/06/apple-introduces-a-delightful-and-elegant-new-software-design/?videoid=c6256ec6b063b61342e3bb1f004919e1</a></p><p>This change impacts UIKit and SwiftUI directly, with new APIs introduced in <strong>Xcode 16</strong> to support it.</p><p>For more details please visit Apple’s Official page, <a href="https://nr.apple.com/Da5u7w7sw3">here</a>.</p><h3>🔨 Xcode 26: AI‑Supercharged, Smarter, Lighter, Better and Developer‑Friendly</h3><p>The new <strong>Xcode 26</strong> makes development faster, cleaner, and smarter:</p><ul><li>⚡ <strong>Faster Launch</strong>: Projects load up to 40% quicker</li><li>📦 <strong>Smaller Size</strong>: Now modular, downloads only what you need</li><li>🤖 <strong>Built-in AI Assistant</strong>: Generate code, fix bugs, and write documentation with inline suggestions</li><li>🔍 <strong>Live Previews</strong>: Debug SwiftUI in real-time with animations</li><li>🛠 <strong>Liquid Glass Toolkit</strong>: Test translucency, blur, and motion natively</li><li>🧪 <strong>Icon Composer</strong>: Create visually rich, depth-aware icons</li><li>☁️ <strong>Xcode Cloud 2025</strong>: Faster CI, TestFlight tools, auto-release notes with AI</li></ul><blockquote><em>Swift Macros and new diagnostics make coding faster and easier than ever.</em></blockquote><p>For more details about Xcode 26, watch <a href="https://developer.apple.com/videos/play/wwdc2025/247">this</a>.</p><h3>📦 Xcode 16 &amp; Developer Tools</h3><ul><li>AI-powered <strong>code suggestions</strong>, doc generation, and refactoring</li><li>Enhanced Previews and runtime debugging for SwiftUI</li><li>New <strong>App Store SDK Insights</strong> to optimize performance and SDK usage post-release</li></ul><h3>🛠️ Swift 6: Modern Concurrency, Macros &amp; More</h3><h4>What’s New:</h4><ul><li><strong>Macros</strong>: Powerful new meta-programming tools for code generation</li><li><strong>Typed throws</strong>: Safer and more predictable error handling</li><li><strong>Improved Concurrency</strong>: Better task cancellation and cooperative scheduling</li><li><strong>SwiftUI 5</strong>: Major layout performance upgrades, animated stacks, scroll transitions</li></ul><blockquote><em>These changes help write cleaner, faster code and integrate AI more efficiently.</em></blockquote><h3>📱 iOS 26 (formerly iOS 19): Apple Intelligence, Siri 2.0 &amp; UI Enhancements</h3><p>iOS 26 is the most AI-driven and developer-centric iOS yet.</p><h4>🔍 Apple Intelligence (On-Device AI)</h4><p>Apple introduced <strong>Apple Intelligence</strong>, a suite of private, on-device AI tools powered by foundation models:</p><ul><li><strong>Text tools</strong>: Summarize, rewrite, proofread in Mail, Messages, and Notes</li><li><strong>Image Playground</strong>: Create AI images and Genmoji directly from prompts</li><li><strong>Contextual Siri</strong>: Now more aware of your screen and able to perform app-specific actions</li><li><strong>Private Cloud Compute</strong>: Secure fallback for intensive AI processing via Apple Silicon servers</li></ul><blockquote><em>Only available on iPhone 16 Pro, iPads and Macs with M-series chips.</em></blockquote><h4>📞 App Updates</h4><ul><li><strong>Phone</strong>: Live voicemail, AI call screening</li><li><strong>Messages</strong>: Scheduled send, polls, Genmoji, live translation</li><li><strong>Camera</strong>: Streamlined UI, smart object removal</li><li><strong>Safari</strong>: Full-screen experience, new highlights view</li></ul><h4>🔋 Smart Battery</h4><p>An <strong>adaptive battery system</strong> that learns your usage and optimised charging behaviour to extend long-term health.</p><h3>🧠 Foundation Models API: AI for Developers</h3><p>Developers now have access to Apple’s <strong>Foundation Models API</strong>, allowing apps to harness generative AI locally:</p><ul><li>Integrate summaries, search, and media generation into your app</li><li>Guided prompt generation, stateful sessions, tool calling</li><li>Train small models for niche use cases</li><li>No internet required; all inference runs securely on-device</li></ul><blockquote><em>Available through Swift with new AI-focused frameworks in Xcode 16.</em></blockquote><h3>🖥 macOS 26 (Tahoe): Intelligence for Productivity</h3><p>macOS now deeply integrates Apple Intelligence:</p><ul><li>Smarter <strong>Spotlight</strong>: Can summarize documents, emails, or open apps</li><li>Phone app on Mac: Make/receive calls from Mac natively</li><li>Privacy Dashboard: See what AI models are processing and when</li></ul><h3>⌚️ watchOS 26: Live Translation &amp; Notes on Your Wrist</h3><ul><li>Live Translate in real-time while traveling</li><li>A new Notes app with voice and scribble support</li><li><em>Workout Buddy</em>: Personalized AI coaching based on your activity</li></ul><h3>👓 Vision Pro + Spatial APIs</h3><p><strong>visionOS 26</strong> makes it easier to bring 2D iOS apps into spatial computing:</p><ul><li>UIKit/SwiftUI support for depth-aware layout</li><li>New spatial APIs for head tracking, gestures, and adaptive input</li><li>Support for real-world object persistence across sessions</li></ul><h3>Final Thoughts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MxRDKAqZVhmUtVBgAjUlZg.png" /></figure><p>Apple’s WWDC 2025 reflects a clear vision: <strong>Privacy-first intelligence</strong>, <strong>immersive UI</strong>, and <strong>developer empowerment</strong>. Whether you’re building apps, designing for Apple devices, or simply a user, the coming year will redefine how we interact with technology.</p><p><em>It’s not just an incremental update — it’s the foundation for the next-gen Apple ecosystem.</em></p><p>✍️ <em>What are you most excited about from WWDC 2025? Drop your thoughts in the comments or connect with me on </em><a href="https://www.linkedin.com/in/satish-iosdev/"><em>LinkedIn</em></a><em>.</em></p><p><strong>Suggestion are always welcome.</strong></p><p>Thanks for reading 🙏.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8134391abad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Pros and Cons of Singleton Pattern in Swift]]></title>
            <link>https://medium.com/@satish24sp/understanding-pros-and-cons-of-singleton-pattern-in-swift-46b7e1f090fa?source=rss-18c588b762c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/46b7e1f090fa</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[singleton-pattern]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[singleton-design-pattern]]></category>
            <dc:creator><![CDATA[Satish Thakur]]></dc:creator>
            <pubDate>Sat, 21 Jun 2025 04:41:24 GMT</pubDate>
            <atom:updated>2025-06-21T04:48:23.652Z</atom:updated>
            <content:encoded><![CDATA[<p>The Singleton pattern is one of the most widely used design patterns in software development.</p><p>It ensures that a class has only one instance and provides a global point of access to that instance. While this pattern can simplify certain scenarios, it also comes with trade-offs that developers need to consider carefully.</p><p>In this article, we’ll explore the benefits and drawbacks, and walk through real code examples to understand where and how it should be used.</p><p>For the details like what is Singleton pattern and how we can create them effectively, please read my other article <a href="https://medium.com/@satish24sp/singleton-design-pattern-in-swift-0b82f23ae473"><strong>Singleton Design Pattern in Swift</strong></a>.</p><h3>✅ Pros of Using Singleton</h3><h4>1. Global Access Point</h4><p>Singletons provide a single point of access to shared resources, making it easy to access a class from anywhere in the app.</p><p>🔍 <strong><em>Example:</em></strong> A UserSessionManager singleton that stores authentication tokens accessible throughout the app.</p><h4>2. Resource Efficiency</h4><p>By ensuring only one instance exists, singletons can help manage memory and resource usage effectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*73gwiNas5PBi53sh6_yrsA.png" /><figcaption>Single instance shared across multiple views</figcaption></figure><h4>3. State Preservation</h4><p>Singletons can maintain the state across the app’s lifecycle, making them suitable for managing shared data.</p><pre>class AppSettings {<br>    static let shared = AppSettings()<br>    private init() {}<br><br>    var isDarkModeEnabled: Bool = false<br>}</pre><h3>❌ Cons of Using Singleton</h3><h4>1. Global State Can Be Risky</h4><p>Since singletons maintain a global state, it can become difficult to track and debug state changes, especially in large apps.</p><p>💡 <strong><em>Tip:</em></strong> Avoid storing mutable state in singletons unless absolutely necessary.</p><h4>2. Harder to Unit Test</h4><p>Singletons introduce implicit dependencies, which makes them harder to mock or replace during unit testing.</p><pre>// Hard to inject mock logger:<br>Logger.shared.log(&quot;Test message&quot;)</pre><p>🔁 <strong><em>Solution:</em></strong> Use dependency injection where possible, even for singletons.</p><h4>3. Tight Coupling</h4><p>When classes rely on singletons, it can lead to tight coupling, making your codebase harder to maintain and refactor.</p><h4>4. Not Suitable for All Use Cases</h4><p>Singletons are often overused. They are best for stateless services (like logging or analytics), but not for storing user data or app state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8vDoCVQ5-x3Av0Vb53xNig.png" /><figcaption>Spiderweb of dependencies caused by overusing singletons</figcaption></figure><h3>🔄 Alternatives to Singleton</h3><ul><li><strong>Dependency Injection</strong>: Pass dependencies explicitly to improve testability and modularity.</li><li><strong>Protocols</strong>: Define interfaces so you can mock dependencies in tests.</li><li><strong>Actor Model (Swift Concurrency)</strong>: Leverage actors for state encapsulation and thread safety.</li></ul><h3>🧪 Test-Friendly Singleton (Bonus)</h3><p>Here’s how you can make your Singleton more testable:</p><pre>protocol Logging {<br>    func log(_ message: String)<br>}<br><br>class Logger: Logging {<br>    static let shared = Logger()<br>    private init() {}<br><br>    func log(_ message: String) {<br>        print(&quot;LOG: \(message)&quot;)<br>    }<br>}<br><br>// In production<br>var logger: Logging = Logger.shared<br><br>// In tests<br>class MockLogger: Logging {<br>    var logs: [String] = []<br>    func log(_ message: String) {<br>        logs.append(message)<br>    }<br>}</pre><h3>✅ When Should You Use a Singleton?</h3><p><strong>Do use Singletons</strong> when:</p><ul><li>You need exactly <strong>one</strong> shared instance.</li><li>Global access makes sense (e.g., App Configuration, UserDefaults).</li><li>You’re managing shared resources.</li></ul><p><strong>Avoid them</strong> when:</p><ul><li>Writing code that should be easy to test.</li><li>The class has mutable shared state that could cause race conditions.</li><li>You’re unsure of the lifetime or ownership of the shared object.</li></ul><h3>📌 Conclusion</h3><p>The Singleton pattern is a powerful tool, but like all tools, it should be used judiciously. While it provides convenience and consistency, overuse can lead to hard-to-maintain and brittle code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OrkYRItik8ioUN0pzW8NWg.png" /></figure><p>If you enjoyed this article, feel free to follow me for more insights into Swift, iOS architecture, and clean coding practices.</p><p><strong><em>If you have any questions, please feel free to ask through the comment or my </em></strong><a href="https://www.linkedin.com/in/satish-iosdev/"><strong><em>LinkedIn Profile</em></strong></a><strong><em>.</em></strong></p><p><strong>Suggestion are always welcome.</strong></p><p>Thanks for reading 🙏.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46b7e1f090fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Singleton Design Pattern in Swift]]></title>
            <link>https://medium.com/@satish24sp/singleton-design-pattern-in-swift-0b82f23ae473?source=rss-18c588b762c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b82f23ae473</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[singleton-pattern]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[singleton]]></category>
            <dc:creator><![CDATA[Satish Thakur]]></dc:creator>
            <pubDate>Sun, 15 Oct 2023 16:02:59 GMT</pubDate>
            <atom:updated>2025-06-21T04:51:31.678Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nu8p-UeY2_3IVeZSB8OCcg.png" /></figure><p>In Swift, <strong>Singleton </strong>is a design pattern that ensures a class can have only one object instance throughout the app memory and provide all the code functionality through a single point of access to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4EbR0UKyTKSH62C3SB9SKw.png" /></figure><blockquote>The singleton pattern guarantees that only one instance of a class is<br>instantiated.</blockquote><p>In common word, Singleton is similar to global variable which can be created at once and use everywhere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*QyLL2reHNHxAi2t3Rh9Kfw.png" /></figure><blockquote><strong>Global</strong> <strong>variable</strong> is initialised at the starting of your program but<br><strong>Singleton</strong> is initialised only the first time whenever you use it.</blockquote><p>Singletons are really common on Apple’s platforms and we have used so many Apple APIs which work on singleton such as</p><p>UIApplication(<em>i.e. UIApplication.shared</em>),</p><p>FileManager(<em>i.e. FileManager.default</em>),</p><p>URLSession(<em>i.e. URLSession.shared</em>),</p><p>SKPaymentQueue(<em>i.e</em>. <em>SKPaymentQueue.default()</em>),</p><p>UserDefaults(<em>i.e. UserDefaults.standard</em>), etc.</p><p>There are three rules to create a Singleton class:</p><ol><li>Initialize a static variable in that class of that same class type</li><li>Singleton class should be final</li><li>Singleton class initializer must be private</li></ol><h3>How we create Singleton Class:</h3><p>Let’s understand this using a example with a normal class and removing their loopholes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/764/1*1cg0QotJJ-jLGEW4KlQvQQ.png" /></figure><p><strong>Class without Singleton Pattern:</strong></p><pre>class UserDetails {<br><br>//MARK: Variable declaration<br>    var name:String = &quot;&quot;<br>    var profession: String = &quot;&quot;<br>    <br>//MARK: Your custom function<br>    func showUserDetails() {<br>        print(&quot;User Name: \(name) \nUser Profession: \(profession)&quot;)<br>    }<br><br>}</pre><p>Now suppose you have to use this function in two different classes or view controllers</p><pre>//MARK: Access the UserDetails class <br>// Initialize for first user<br>let userFirst = UserDetails()<br>userFirst.name = &quot;Navdeep&quot;<br>userFirst.profession = &quot;iOS developer&quot;<br>userFirst.showUserDetails()<br><br>// Initialize for second user<br>let userSecond = UserDetails()<br>userSecond.name = &quot;Ashutosh&quot;<br>userSecond.profession = &quot;FullStack developer&quot;<br>userSecond.showUserDetails()</pre><p>Here, you can see for each users we have to initialize it everytime by creating a new instance of UserDetails class and due to this multiple allocation &amp; deallocation of memory would takes place. So to avoid creating multiple instances or class initializations, we need to make a <strong>static instance</strong>.</p><h4><strong>Rule 1: Initialize a static variable in that class of that same class type</strong></h4><p>Making the object static allows us to access the object using the class name. And due to this static instance it can be accessible globally.</p><p><strong>Class with Basic Singleton Pattern:</strong></p><pre>class UserDetails {<br>    <br>    //MARK: Variable declaration<br>    var name:String = &quot;&quot;<br>    var profession: String = &quot;&quot;<br>    <br>    static let shared = UserDetails()  // static property to create singleton<br>    <br>    init(){}                           // default initializer<br>    <br>    //MARK: Your custom function<br>    func showUserDetails() {<br>        print(&quot;User Name: \(name) \nUser Profession: \(profession)&quot;)<br>    }<br>    <br>}</pre><blockquote><strong><em>Static </em></strong><em>properties and methods are lazy initialize by default meaning that it will not be instantiated until it is being called, therefore provides some optimization.</em></blockquote><p>Now, when we want to use the UserDetails, we can simply use</p><pre>//MARK: Access the UserDetails class using singleton pattern<br>// Initialize for first user<br>let userFirst = UserDetails.shared<br>userFirst.name = &quot;Navdeep&quot;<br>userFirst.profession = &quot;iOS developer&quot;<br>userFirst.showUserDetails()<br><br>// Initialize for second user<br>let userSecond = UserDetails.shared<br>userSecond.name = &quot;Ashutosh&quot;<br>userSecond.profession = &quot;FullStack developer&quot;<br>userSecond.showUserDetails()<br><br>// Initialize for third user without singleton<br>let userThird = UserDetails()<br>userThird.name = &quot;Abhishek&quot;<br>userThird.profession = &quot;Senior iOS developer&quot;<br>userThird.showUserDetails()</pre><p>Here, you can see we are using the same static instance for creating userFirst and userSecond and only one memory allocation &amp; deallocation needed for the shared instance.</p><blockquote>But there are still a loop holes, right now anyone can create and alter singleton class and still use your singleton class as a normal class just like the above one i.e. <strong>Class without singleton pattern, </strong>due to class default initalizer e.g. see above instance creation for userThird.</blockquote><blockquote><strong>So, we need to consider two most important points while creating singleton class</strong></blockquote><blockquote>1. Singleton class should not be extendable.</blockquote><blockquote>2. Singleton classes should not be initiate outside the class itself.</blockquote><h4>Rule 2: Singleton class should be final</h4><p><strong><em>final</em></strong> keyword help us to prevent inheritance means no other class can subclass the singleton class.</p><pre>final class UserDetails {              // use to prevent inheritance<br>    <br>    //MARK: Variable declaration<br>    var name:String = &quot;&quot;<br>    var profession: String = &quot;&quot;<br>    <br>    static let shared = UserDetails()  // static property to create singleton<br>    <br>    init(){}                           // default initializer<br>    <br>    //MARK: Your custom function<br>    func showUserDetails() {<br>        print(&quot;User Name: \(name) \nUser Profession: \(profession)&quot;)<br>    }<br>    <br>}</pre><p>So now you are not able to change the behaviour of the final class and we are required to follow the same implementation throughout all the derived classes.</p><h4>Rule 3: Singleton class initializer must be private</h4><p>By default, every class initializer is public and anyone can create their object instance as per their need just like normal class.</p><p>So to restrict the object creation from outside the class, we need to add private initializer in our singleton class.</p><blockquote>Adding a <strong>private</strong> initializer is important, because it stops other parts of our code from trying to create a class instance. However, the class creates its own instance of itself as a static variable, which means the only instance of the class is the one it created.</blockquote><pre>final class UserDetails {              // use to prevent inheritance<br>    <br>    //MARK: Variable declaration<br>    var name:String = &quot;&quot;<br>    var profession: String = &quot;&quot;<br>    <br>    static let shared = UserDetails()  // static property to create singleton<br>    <br>    private init(){}                   // private initializer<br>    <br>    //MARK: Your custom function<br>    func showUserDetails() {<br>        print(&quot;User Name: \(name) \nUser Profession: \(profession)&quot;)<br>    }<br>    <br>}</pre><p>After changing the default initializer to private initializer, you are not able to create new object and will see the error like below attached screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YYlh5DGhzLkSpBkCgm00jg.png" /><figcaption>Default initializer access change to private initializer</figcaption></figure><h3>Finally, your fully protected singleton class is ready for use.</h3><p>And now you can use your singleton class as:</p><pre>// Initialize for third user<br>let userThird = UserDetails.shared<br>userThird.name = &quot;Ashutosh&quot;<br>userThird.profession = &quot;FullStack developer&quot;<br>userThird.showUserDetails()</pre><h3>Important Suggestion:</h3><p>Yes, Singleton can solve the problem of multiple object creations but it has some drawbacks as well. One of the main drawbacks of using the singleton pattern is that it can reduce the scalability and testability of your application.</p><p>Please find the details about the pro &amp; cons as well as available alternate of singleton in my another posts 👇🏻</p><p><a href="https://medium.com/@satish24sp/understanding-pros-and-cons-of-singleton-pattern-in-swift-46b7e1f090fa"><strong>Understanding Pros and Cons of Singleton Pattern in Swift</strong></a></p><p><strong><em>If you have any questions, please feel free to ask through the comment or my </em></strong><a href="https://www.linkedin.com/in/satish-iosdev/"><strong><em>LinkedIn Profile</em></strong></a><strong><em>.</em></strong></p><p><strong>Suggestion are always welcome.</strong></p><p>Thanks for reading 🙏.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b82f23ae473" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Firebase dynamic link deprecation and its alternates]]></title>
            <link>https://medium.com/@satish24sp/firebase-dynamic-link-deprecation-and-its-alternates-81d72e33734?source=rss-18c588b762c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/81d72e33734</guid>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-app-links]]></category>
            <category><![CDATA[dynamic-link]]></category>
            <dc:creator><![CDATA[Satish Thakur]]></dc:creator>
            <pubDate>Thu, 28 Sep 2023 18:20:54 GMT</pubDate>
            <atom:updated>2025-07-22T01:46:34.396Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mFyA2LEDWTNYzhUeHWzR2Q.png" /><figcaption>Sunset of firebase dynamic linking</figcaption></figure><p><strong>About</strong><br>Many of us use and are familiar with the Firebase dynamic linking framework/library for creating the links and sharing with the users, but now Google decided to shut down this service from 25th August 2025.</p><p>This documentation contains information about the Firebase dynamic link depreciation, its use cases and alternative solutions.</p><p>So let’s start from the basics.</p><p>This documentation is divided into two parts.<br><strong>Part 1</strong> will contain the basics about dynamic links, why we need them and their use case, etc. and<br><strong>Part 2</strong> will contain the details about the Firebase dynamic linking deprecation, migration date, whether new/old links work or not and many more.</p><h3><strong>PART 1</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vu0a3KI-jV2BBY4eoZNHUQ.png" /></figure><p><strong>What is a dynamic link?</strong><br>A dynamic link is a replacement link, similar to a URL shorter for another link. But it behaves<br>differently based on the platform it is opened on and this behaviour can be programmed by the<br>developer(you).</p><p><strong>Why do we need dynamic links?</strong><br>With Dynamic Links, users get the best available experience for the platform they open your link on.<br>If a user opens a Dynamic Link on iOS or Android, they can be taken directly to the linked content in<br>your native app.<br>If a user opens the same Dynamic Link in a desktop browser, they can be taken to the equivalent content on your website.</p><p>In addition, Dynamic Links work across app installs: if a user opens a Dynamic Link on iOS or Android and doesn’t have your app installed, the user can be prompted to install it; then, after installation, your app starts and can access the link.</p><p><strong>How does it work?</strong><br>When a user opens one of your Dynamic Links, if your app isn’t yet installed, the user is sent to the Play Store or App Store to install your app (unless you specify otherwise), and your app opens. You can then retrieve the link that was passed to your app and handle the deep link as appropriate for your app.</p><p><strong>What is the benefit(s) of using it?</strong><br>👉 Grow your app install and user base fast.<br>👉 Building a marketplace: Every listing shared by the users can convert viewers into installed app users. <em>Eg. Airbnb</em><br>👉 Building a social platform: Each post can lead to app installation and user acquisition. <em>Eg. X(formerly Twitter)</em><br>👉 Password reset emails can convert our web app users to installed app users.</p><p>And since you can send native push notifications to installed app users, you have a direct line of communication with your customers. They are also more loyal and likely to lead to additional users for you. All of this with no customer acquisition cost or marketing spend.</p><p><strong>Example use cases</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L16maF_3Ck1JiPyC273Ptg.png" /><figcaption>Basic use cases</figcaption></figure><p>Here are some example use cases which Firebase also suggests in its documentation.<br><strong>1. Converting web users to app users</strong><br>Without Dynamic Links, if a mobile web user installs your app by opening an app install link, they have to re-navigate to where they were.<br>With Dynamic Links, you can ensure that after a web user installs your app, they can continue where they left off.</p><p><strong>2. Social, emails and SMS campaigns</strong><br>Send promotional offers using links that work on any platform. Current and future users can redeem your offers whether they use iOS, Android, or a web browser, and whether or not they already have your app installed.</p><p><strong>3. User-to-user sharing<br></strong>Make it easy for your users to share your app’s content with their friends, no matter what platform their friends use, or whether their friends already use your app.</p><p><strong>4. Converting desktop users to app users</strong><br>Generate Dynamic Links when web users bookmark a page or send themselves a link. When they open the link on a different device, they can get the best experience for the device.</p><p><strong>5. Real-world app promotion</strong><br>Use QR codes that encode a Dynamic Link in your physical displays to promote your app at events and venues. Imagine if Starbucks could convert every user payment from a mobile device into an app-installed user, how valuable its app would be today. <em>Eg. Haldiram and Domino’s</em></p><p><strong>6. Customized user referrals</strong><br>Accelerate growth by providing an incentive for your users to invite their friends. Invitation links based on dynamic links work across platforms. New users opening your app for the first time get a first-run experience that you customize for them.<br><em>For example, you can automatically connect them with the friend that invited them. Optionally delay granting rewards until new users complete some introductory task, such as completing a tutorial.</em></p><h3><strong>PART 2</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*xkYi_jW-t0d8pgLEGZQTkQ.jpeg" /></figure><p><strong>What do I need to know?</strong><br><strong><em>On August 25th, 2025, Firebase Dynamic Links will shut down. </em></strong>All links served by Firebase Dynamic Links (both hosted on custom domains and page.link subdomains) will stop working and you will no longer be able to create new links.</p><p><strong>Why is the Firebase dynamic link going to deprecate?</strong><br>Firebase Dynamic Links over 7 years ago to make URLs more powerful — for example, dynamically changing the destination of a link based on run-time conditions.</p><p>Now, the original native APIs that Firebase Dynamic Links were built on have evolved and presented new challenges and due to this the ideal user or seamless experience is impacted.</p><p><strong>How much time is left to migrate?</strong><br>Until August 25th, 2025 you have to complete your migration.</p><p><strong>What about new and existing links?</strong><br>Until August 25th, 2025, the new and existing links will continue to work.</p><p><strong>What do you need to do?<br></strong>Take the following actions before <strong>August 25, 2025</strong>:</p><p>👉 Review your use cases to evaluate, decide and potentially adopt alternative solutions</p><p>👉 Complete your migration from Firebase Dynamic Links</p><p>👉 Delete your domain prefixes from Firebase Dynamic Links when you have successfully migrated your links and use-cases</p><p><em>Please note that your domain prefixes and any created links will be automatically removed on August 25, 2025, and Firebase Dynamic Links will no longer be available for your project.</em></p><p><strong>What will happen to our links after August 25th, 2025 or service shutdown, is there any negative impact on the app?<br></strong>👉 All links clicked will return an HTTP 404 status response to end users.</p><p>👉 All HTTP requests to the below-mentioned URLs will return a 400/403 HTTP Status response.</p><ul><li><a href="https://firebasedynamiclinks.googleapis.com/v1/shortLinks">https://firebasedynamiclinks.googleapis.com/v1/shortLinks</a> (Short Links API)</li><li><a href="https://firebasedynamiclinks.googleapis.com/v1/SHORT_DYNAMIC_LINK/linkStats">https://firebasedynamiclinks.googleapis.com/v1/SHORT_DYNAMIC_LINK/linkStats</a> (Link Stats API)</li></ul><p>Also, if an application is handling the Firebase failure response, then the app will not crash, else you need to handle it before the Firebase dynamic link sunset.</p><h3><strong>What are the alternatives available?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*K8jZwi8FDkCVSdFJqXRQ-g.png" /></figure><p><strong>Native alternates:<br></strong>Over the years, the web and mobile ecosystems have evolved with technologies and have made user journeys across apps and the web more seamless and predictable for our app users. Native alternatives such as</p><p>👉 <a href="https://developer.android.com/training/app-links">App Links</a>,</p><p>👉 <a href="https://developer.android.com/topic/google-play-instant/overview">Google Play Instant</a>,</p><p>👉 <a href="https://developer.apple.com/ios/universal-links/">Universal Links</a>, and</p><p>👉 <a href="https://developer.apple.com/app-clips/">App Clips</a></p><p><strong>3rd Party alternates:<br></strong>Currently, there are many service providers/vendors available in the market which provide similar functionality to Firebase dynamic links, and you can choose according to your app preference and needs such as</p><p>👉 <a href="https://1link.io/?ref=satish">1Link.IO</a></p><p>👉 <a href="https://www.branch.io/">Branch.IO</a>,</p><p>👉 <a href="https://app.urlgeni.us/">URLgenius</a>,</p><p>👉 <a href="https://dash.adjust.com/">Adjust</a>,</p><p>👉 <a href="https://www.appsflyer.com/">AppsFlyer</a>,</p><p>👉 <a href="https://bitly.com/">Bitly</a>,</p><p>👉 <a href="https://www.kochava.com/">Kochava</a></p><p><strong>Reference source💡</strong></p><p>👉 <a href="https://bdk.crisp.help/en-us/article/understanding-dynamic-links-ie-programmable-deeplinks-11tbkf8/">Understanding Dynamic Links</a></p><p>👉 <a href="https://firebase.google.com/support/dynamic-links-faq">Dynamic Links Deprecation FAQ</a></p><p>👉 <a href="https://1link.io/firebase-dynamic-links-migration/?ref=satish/#technical-deep-linking-setup">1Link.IO Integration guide</a></p><p><strong><em>If you have any questions, please feel free to ask through the comment or my </em></strong><a href="https://www.linkedin.com/in/satish-iosdev/"><strong><em>LinkedIn Profile</em></strong></a><strong><em>.</em></strong></p><p><strong>Suggestion are always welcome.</strong></p><p>Thanks for reading 🙏.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81d72e33734" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[iOS 16 requires special Developer Mode to run the apps from XCode or External Links]]></title>
            <link>https://medium.com/@satish24sp/ios-16-requires-special-developer-mode-to-run-the-apps-from-xcode-or-external-links-47d078c99260?source=rss-18c588b762c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/47d078c99260</guid>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios-16]]></category>
            <category><![CDATA[developer-mode]]></category>
            <category><![CDATA[ios-16-beta]]></category>
            <dc:creator><![CDATA[Satish Thakur]]></dc:creator>
            <pubDate>Thu, 22 Sep 2022 07:17:20 GMT</pubDate>
            <atom:updated>2022-09-22T07:17:20.776Z</atom:updated>
            <content:encoded><![CDATA[<p>As explained by Apple in a <a href="https://developer.apple.com/videos/play/wwdc2022/110344/">session at WWDC 2022</a>, some of the features used by developers to allow them to side-load their apps during the development process now come turned off by default in iOS 16. According to the company, this is a security measure to prevent malicious apps from using developer tools for targeted attacks.</p><p>With <strong>iOS 16</strong>, Apple is making some changes to prevent attackers from side-loading malicious apps on the device — which includes the addition of a new <strong>Developer Mode</strong>.</p><p>However, these changes caused a bug in the first beta of iOS 16 that also requires this mode for TestFlight apps.</p><p>But we need not to worry ☹️ &amp; thanks to <strong>Apple</strong>, Apple has confirmed that <strong>TestFlight and Enterprise apps</strong> will not require Developer Mode to run since they already have a valid certificate, so the alert is just a bug that will be fixed in a future update.</p><p>So, now the case remains for the developers or users who try to install the build <strong>.ipa</strong> file using the <strong>Xcode</strong>, <a href="https://support.apple.com/apple-configurator"><strong>Apple Configurator</strong></a> as well as any external link such as<strong> </strong><a href="https://www.diawi.com/"><strong>Diawi</strong></a><strong>, </strong><a href="https://www.installonair.com/"><strong>InstallOnAir</strong></a><strong> </strong>or something else, you will see a alert which says</p><p><strong><em>“YourAppName” requires Developer Mode to run. Until Developer Mode has been enabled this app will not be available for use</em>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z4GmFUL7x5WOvlVXwfAEXA.jpeg" /></figure><p>So, before installing the app in your <strong>physical device or Simulator </strong>using XCode build system, Apple Configurator or any external links you need to enable the developer mode first.</p><h3><strong>Installing a build from XCode Build System:</strong></h3><p>When you first connect an iOS device to your Mac, the Xcode scheme selector’s destination list shows it as an “Unavailable Device”, because Developer Mode is disabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/1*TgBF0rr_yaqakN_7i3olrA@2x.png" /></figure><p>The Devices and Simulators window shows a similar banner if you have a device connected with Developer Mode disabled.</p><p>If you attempt to build and run to the device, Xcode displays an alert to tell you the destination isn’t valid because Developer Mode is disabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/253/1*JTOiGEGKwkPIRTK4ymT26A@2x.png" /></figure><h3><strong>How to enable Developer Mode on Apple iPhone running iOS 16:</strong></h3><p>Step 1: Open the Settings application on your Apple iPhone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*rsVDvB-rQsCeColC6SwWzQ.png" /></figure><p>Step 2: When the app opens, select the “Privacy &amp; Security” option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*VSEzbsQshyvJwh6ZJkTLSg.png" /></figure><p>Step 3: In the new page that loads, tap on the “Developer Mode” option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*SUU4MUD_Lirv6vaes_duPw.png" /></figure><p>Step 4: After that, toggle the switch <strong>ON</strong> for the Developer Mode option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*23Ktg7eiEIh7076iVqiqOA.png" /></figure><p>Step 5: You will see a prompt asking to restart the smartphone. Select the “Restart” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*zgb9uU5KxY1S6NFUpJ-1zw.png" /></figure><p>When you unlock your iPhone, a prompt should appear on the screen asking you whether you wish to turn on Developer Mode on your device.<br> Tap <strong>Turn On</strong> inside this prompt, as seen in the image below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*4lkuWGmTKnD_IjVhuCckAA.png" /></figure><h3><strong>How to disable Developer Mode on Apple iPhone running iOS 16:</strong></h3><p>Step 1: Open the Settings application on your Apple iPhone.</p><p>Step 2: When the app opens, select the “Privacy &amp; Security” option.</p><p>Step 3: In the new page that loads, tap on the “Developer Mode” option.</p><p>Step 4: After that, toggle the switch <strong>OFF</strong> for the Developer Mode option.</p><p>Step 5: You will see a prompt asking to restart the smartphone. Select the “Restart” button.</p><h3><strong>What to do if developer mode is not showing, 🤔 :</strong></h3><p>Step 1: Open your project in XCode.</p><p>Step 2: Connect Your iPhone Device.</p><p>Step 3: Open the Settings application on your Apple iPhone.</p><p>Step 4: When the app opens, select the “Privacy &amp; Security” option.</p><p>Step 5: In the new page that loads, tap on the “Developer Mode” option.</p><p><strong><em>If you have any questions, please feel free to ask through the comment or my </em></strong><a href="https://www.linkedin.com/in/satish-iosdev/"><strong><em>LinkedIn Profile</em></strong></a><strong><em>.</em></strong></p><p><strong>Source:</strong> <a href="https://developer.apple.com/documentation/xcode/enabling-developer-mode-on-a-device">Apple</a>, <a href="https://developer.apple.com/wwdc22/">WWDC</a>.</p><p>Thanks for reading 🙏.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47d078c99260" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Share iOS app .ipa file to client or tester without going through Apple TestFlight process]]></title>
            <link>https://medium.com/@satish24sp/share-ios-app-ipa-file-to-client-or-tester-without-going-through-apple-testflight-process-4e3b099c3dec?source=rss-18c588b762c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e3b099c3dec</guid>
            <category><![CDATA[app-store]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[itunes]]></category>
            <dc:creator><![CDATA[Satish Thakur]]></dc:creator>
            <pubDate>Sat, 27 Jun 2020 08:39:53 GMT</pubDate>
            <atom:updated>2020-06-27T08:39:53.971Z</atom:updated>
            <content:encoded><![CDATA[<h3>Share iOS app .ipa file to client or tester without going through Apple TestFlight process</h3><p><strong>[ IMPORTANT NOTE:</strong></p><ol><li><strong>The client device or tester device UUID should be added in trusted device or device list on Apple </strong><a href="https://developer.apple.com/account/resources/devices/list"><strong>appstore</strong></a><strong> only then they will able to install the application.</strong></li><li><strong>Only 100 UUID you are able to add in a particular developer account.]</strong></li></ol><p>Sometimes we have to face problem in sharing iOS .ipa using Testflight with our remote client or testers.<br>And we have many questions in our mind like</p><ul><li><strong><em>How to share .ipa with client or tester.</em><br><em>- Share .ipa without testflight process.</em><br><em>- App failed the testflight review process but still need to send build with client or tester.</em><br><em>- Testflight process is time consuming, how to share .ipa in a easy way.</em><br><em>- Fastest way to share .ipa with client or tester.</em></strong></li></ul><p><strong>So, Here I’m sharing my answer for such questions</strong> in two parts:</p><ol><li>Create .ipa file</li><li>Share .ipa file</li></ol><p><strong>STEPS TO ACHIEVE OUR GOAL OF SHARING .IPA:</strong></p><p><strong><em>1. CREATE .IPA FILE</em></strong><br>Step 1: Select the iOS Device then Go to <strong>Product Tab</strong> → <strong>Compile</strong> and <strong>Build</strong> Your Project Successfully.<br>Step 2: Select the iOS device → <strong>Generic iOS Device</strong><br>Step 3: Go to the <strong>Product</strong> Tab and click on <strong>Archive</strong> to make an archive of your workspace or project.<br>Step 4: Once after achieve is successfully done, Go to the <strong>Window</strong> Tab → Click <strong>Organizer</strong><br>Step 5: Select your archive from the list of archives and click on <strong>Distribute App</strong>.<br>Step 6: Select method of distribution as <strong>ad Hoc</strong> and click <strong>Next</strong> then select ad Hoc distribution option and select <strong>App thinning</strong> as NONE for all device and click <strong>Next</strong><br>Step 7: Select Signing Method as automatically signing or manual signing and click <strong>Next</strong><br>Step 8: After successful compilation, you will see <strong>Export</strong> button and click <strong>Export</strong><br>Step 9: Export the archive to desired location and after that Open the Export Folder you will see your .ipa file</p><p><strong><em>2. SHARE .IPA FILE</em></strong><br>Step 10: Open <a href="https://www.diawi.com/">Diawi</a> or <a href="https://www.installonair.com/">InstallOnAir</a> and drag your .ipa file<br>Step 11: After successfully uploading you will get the link or url for your .ipa<br>Step 12: Share the link with client or tester, and say them to open it on safari browser to install the .ipa</p><p><strong>Hurray :) :) Its done and successfully installed.</strong><br><strong>Suggestion are always welcome</strong></p><p><strong>HAPPY CODING</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e3b099c3dec" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>