DEV Community: divyesh vekariya

Are you a Senior iOS Developer who is seeking new opportunities ?

divyesh vekariya — Mon, 30 Mar 2026 13:45:03 +0000

divyesh vekariya

Mar 28

The Complete Senior iOS Developer Interview Guide (2026)

#ios #swift #interview #mobile

Comments

1 min read

[Boost]

divyesh vekariya — Mon, 30 Mar 2026 13:43:48 +0000

divyesh vekariya

Mar 28

The Complete Senior iOS Developer Interview Guide (2026)

#ios #swift #interview #mobile

Comments

1 min read

The Complete Senior iOS Developer Interview Guide (2026)

divyesh vekariya — Sat, 28 Mar 2026 08:35:39 +0000

After years of building iOS apps and participating in interview processes, I realized something important:

Senior interviews aren’t about memorizing answers. They’re about how you think.

Most developers prepare by revising concepts, APIs, and common questions. That’s useful—but it’s not enough at the senior level.

What interviewers really look for is:

Your ability to explain why you made certain decisions
How you evaluate trade-offs in architecture and design
Whether you can identify edge cases and hidden pitfalls
How clearly you communicate complex ideas

This is what separates a senior engineer from a mid-level one.

What’s inside:

Real-world interview questions
Deep explanations (not just definitions)
Common mistakes and how to avoid them
System-level thinking and decision-making

💡 Disclaimer: This is based on my personal experience and is not affiliated with any company.

If you're preparing for senior iOS roles, I hope this helps you think more clearly and approach interviews with confidence.

Would love to hear your thoughts—what do you think is the hardest part of senior-level interviews?

👉 Read the full guide here:
https://medium.com/@dkvekariya/the-complete-senior-ios-developer-interview-guide-2026-3ec09ab25987

#ios #swift #devcommunity #programming #career

Building QR Code Generator and Scanner with SwiftUI

divyesh vekariya — Mon, 23 Feb 2026 14:45:20 +0000

Mastering QR Code Generation & Scanning in SwiftUI

divyesh vekariya ・ Feb 23

#swift #ios #swiftui #mobile

Mastering QR Code Generation & Scanning in SwiftUI

divyesh vekariya — Mon, 23 Feb 2026 14:44:36 +0000

🔲 QR codes look simple. But they’re powerful.

Most apps treat QR as just another feature.

I recently built a QR Code Generator & Scanner in SwiftUI — and it reminded me that QR is not a UI component…

It’s an offline data bridge.

Here’s what’s actually happening:

Text → Encoded using Core Image → Rendered as QR → Scanned via AVFoundation → Decoded instantly → Triggers real app behavior

That means QR can power:

Offline authentication
Secure device pairing
Payment flows
Deep linking
Data sharing without internet

The most interesting part?
iOS does the heavy lifting — you just need to structure the pipeline correctly.

*I wrote a detailed breakdown of the full generation & scanning architecture here *👇
Mastering QR Code Generation & Scanning in SwiftUI

If you're building QR-based features (payments, login, pairing), I’d love to exchange ideas.

iOSDevelopment #SwiftUI #AVFoundation #CoreImage #SoftwareEngineering #MobileDevelopment

Is Native iOS Development with Swift Still Worth It in 2025?

divyesh vekariya — Wed, 15 Oct 2025 14:30:00 +0000

Focused on creating a high‑quality iOS app and want the best performance and tightest integration? I came across this article: Swift vs. Kotlin vs. Flutter in App Development: What to Choose?

After reading, I’m convinced that Swift is still the safest bet for a truly polished iOS app. Key reasons:

Maximum performance and responsiveness on iOS

Full access to latest Apple APIs/features

Strong support and stability from Apple

But is going native (Swift) justifiable when cross‑platform tools are so mature now? Would you pick Swift over Flutter (or Kotlin) if your app is iOS‑only?

What’s your take — is native iOS via Swift still the gold standard in 2025?

Maximum performance and responsiveness on iOS

Full access to latest Apple APIs/features

Strong support and stability from Apple

But is going native (Swift) justifiable when cross‑platform tools are so mature now? Would you pick Swift over Flutter (or Kotlin) if your app is iOS‑only?

What’s your take — is native iOS via Swift still the gold standard in 2025?

Is Flutter Still the Best Choice in 2025?

divyesh vekariya — Sat, 11 Oct 2025 05:52:27 +0000

Thinking of building a mobile app for both iOS and Android?
Check out this article: Swift vs. Kotlin vs. Flutter in App Development: What to Choose

Swift vs. Kotlin vs. Flutter in App Development: What to Choose? | by Rahim Ladhani | Medium

Rahim Ladhani ・ May 28, 2025 ・
nevinainfotech25.Medium

After reading it, I’m leaning heavily toward Flutter.
Why? Because:

One single codebase saves time and effort

Strong UI capabilities and flexibility

Good balance between cost and speed to market

Performance almost like native(For simple app without core api)

But is Flutter really good enough compared to native iOS/Android now?
Or are there critical trade‑offs (performance, native API access) that make it risky for some projects?

What do you think — for a cross‑platform mobile app in 2025, would you choose Flutter, or go native instead?

Latest iOS 26 TextKit API's

divyesh vekariya — Mon, 06 Oct 2025 06:26:14 +0000

How to Build Rich Text Editor in SwiftUI

divyesh vekariya ・ Oct 6

#swiftui #swift #ios #development

How to Build Rich Text Editor in SwiftUI

divyesh vekariya — Mon, 06 Oct 2025 06:23:14 +0000

Building a Rich Text Editor in SwiftUI (with iOS 26 APIs)

I am spending weekends exploring new iOS features — and this time, I went deep into the latest SwiftUI text APIs in iOS 26. The goal? To build a fully native Rich Text Editor — no UIKit, no hacks, just clean SwiftUI.

Apple’s new text stack has evolved a lot — with AttributedString, AttributedTextSelection, and transformAttributes(in:), it’s finally possible to manage styles like bold, italic, and underline directly in SwiftUI while keeping everything performant and elegant.

In my full article, I dive into how to:
✅ Build toolbar actions for bold, italic, underline
✅ Keep toolbar state synced with selection
✅ Handle serialization for saving styled text

It’s amazing how much cleaner things have become with the new APIs — definitely one of my favorite updates in iOS 26.

Check out the full write-up here: https://medium.com/@dkvekariya/how-to-build-rich-text-editor-in-swiftui-f09a39d2dce9

Free GraphQL APIs You Can Use Today

divyesh vekariya — Thu, 08 May 2025 05:55:07 +0000

Whether you're building a demo, running a workshop, or just learning how GraphQL works, it's always easier with real examples. While Apollo Server makes spinning up your own API smooth, sometimes you just want something ready to go.

Good news: there are several public GraphQL APIs you can use for free. Here are eight of them, complete with sample queries to get you started.

1. SpaceX API

Get information about past launches, rockets, and more.

Example Query:

{
  launchesPast(limit: 10) {
    mission_name
    launch_date_local
    launch_site {
      site_name_long
    }
    links {
      article_link
      video_link
    }
    rocket {
      rocket_name
    }
  }
}

Try it here

2. SWAPI (Star Wars API)

For Star Wars fans. Great for showing how GraphQL handles nested relationships.

Example Query:

{
  allFilms {
    films {
      title
    }
  }
}

Try it here

3. Rick and Morty API

Fetch characters, episodes, and locations from the Rick and Morty universe.

Example Query:

{
  characters(page: 2, filter: { name: "rick" }) {
    info {
      count
    }
    results {
      name
    }
  }
}

Try it here

4. Countries API

Get info on country names, codes, and emoji.

Example Query:

{
  countries {
    code
    name
    emoji
  }
}

Try it here

5. PokeAPI (GraphQL Wrapper)

All the data needed for a Pokédex. Rate-limited and free for non-commercial use.

Example Query:

{
  gen1_species: pokemon_v2_pokemonspecies(
    where: { pokemon_v2_generation: { name: { _eq: "generation-i" } } }
    order_by: { id: asc }
  ) {
    name
    id
  }
}

Try it here

6. DexAPI

Another Pokémon API, fast and great for quick queries. Still in early development.

Example Query:

{
  allPokemon {
    name
  }
}

Try it here

7. Anilist API

Access thousands of anime titles. Free for non-commercial use with generous rate limits.

Example Query:

{
  Page {
    media {
      siteUrl
      title {
        english
        native
      }
      description
    }
  }
}

Try it here

8. GitHub API

A robust API perfect for real-world GraphQL exploration. Supports queries and mutations.

Note: You’ll need a personal access token and must add an Authorization header in Apollo Explorer.

Example Query:

{
  viewer {
    login
    repositories(last: 10) {
      nodes {
        name
      }
    }
  }
}

Check the docs

These public APIs are perfect for practicing GraphQL without setup headaches. Whether you're exploring schema design or teaching a class, these options have you covered.

Happy Coding...

iOS 19 SDK Developer Update: Prepare for UIApplicationDelegate Deprecations

divyesh vekariya — Mon, 28 Apr 2025 05:06:01 +0000

Dear iOS Developers,

Recent WebKit commits signal that Apple is planning to deprecate several legacy UIApplicationDelegate methods in the iOS 19 SDK, expected to be unveiled at WWDC 2025. This move continues Apple’s transition, started with iOS 13, toward UISceneDelegate for modern app lifecycle management. Below, we outline the changes, their implications, and steps to ensure your apps remain future-proof.

Affected APIs

The following UIApplicationDelegate methods are slated for deprecation in the iOS 19 SDK:

application(_:open:options:)
applicationWillResignActive(_:)
applicationDidEnterBackground(_:)
applicationWillEnterForeground(_:)
applicationDidBecomeActive(_:)
applicationWillTerminate(_:)

These methods have been central to managing app lifecycle events, but Apple is now favoring UISceneDelegate equivalents to support multi-window and scene-based architectures introduced in iOS 13.

What Does Deprecation Mean?

Deprecation is Apple’s way of signaling that these APIs are no longer recommended for use. While deprecated APIs typically remain functional for several iOS versions, they may not receive updates, could exhibit compatibility issues, and will eventually be removed. For reference, APIs like UIWebView (deprecated in iOS 12) lingered for years but faced App Store submission restrictions by 2020.

The deprecation of these UIApplicationDelegate methods doesn’t mean immediate removal in iOS 19, but it’s a clear directive to migrate to UISceneDelegate to ensure long-term compatibility.

Why the Shift to UISceneDelegate?

Since iOS 13, Apple has encouraged developers to adopt UISceneDelegate for lifecycle management, offering:

Multi-Window Support: UISceneDelegate enables apps to manage multiple scenes, crucial for iPadOS and visionOS.
Granular Lifecycle Control: Scene-based APIs provide finer control over individual windows or scenes compared to the app-wide UIApplicationDelegate.
Future-Proofing: Aligning with Apple’s modern frameworks, including SwiftUI, ensures compatibility with emerging features like Stage Manager and visionOS.

This shift also reflects Apple’s broader ecosystem goals, where UISceneDelegate is the foundation for multi-window experiences across iOS, iPadOS, and beyond.

Action Plan for Developers

To prepare for iOS 19 and beyond, we recommend the following steps:

Audit Your Codebase:
- Identify usage of the deprecated UIApplicationDelegate methods.
- Use Xcode’s warnings and documentation to pinpoint reliance on these APIs.
Migrate to UISceneDelegate:
- Adopt UISceneDelegate methods, such as scene(_:willConnectTo:options:), sceneDidBecomeActive(_:), and sceneDidEnterBackground(_:).
- For apps supporting iOS 13 and later, implement scene-based lifecycle management. Apple’s Managing Your App’s Life Cycle guide is a great starting point.
- If supporting iOS 12 or earlier, use conditional checks to maintain compatibility (e.g., if #available(iOS 13.0, *)).
Test Thoroughly:
- Test your app on iOS 18.4 simulators with Xcode 16.3 to ensure no unexpected behavior.
- When iOS 19 SDK betas become available, test early to catch any deprecation-related issues.
Leverage SwiftUI (Optional):
- For new projects or major refactors, consider SwiftUI’s lifecycle management, which integrates seamlessly with scene-based APIs and reduces reliance on traditional delegates.
Plan for App Store Compliance:
- Apple may enforce stricter App Store guidelines in the future 2025 or later, potentially rejecting apps using deprecated APIs. Proactively migrating now will avoid future submission issues.

Example Migration

Here’s a basic example of transitioning from UIApplicationDelegate to UISceneDelegate:

Before (UIApplicationDelegate):

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
    // App setup code
    return true
}

func applicationDidBecomeActive(_ application: UIApplication) {
    // Handle active state
}

After (UISceneDelegate):

func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions) {
    // App setup code
}

func sceneDidBecomeActive(_ scene: UIScene) {
    // Handle active state
}

For a complete guide, refer to Apple’s UISceneDelegate documentation.

Community Discussion

The iOS developer community is already buzzing about this change. Posts on X suggest some developers are concerned about the transition, while others see it as a natural evolution toward UISceneDelegate. Join the conversation on platforms like Reddit’s r/iOSProgramming or Apple Developer Forums to share insights and solutions.

Stay Ahead

To stay informed, keep an eye on WebKit commits and Apple’s developer documentation for early signals of SDK changes. WWDC 2025 (likely June) will likely provide official confirmation and detailed guidance on iOS 19’s changes.

By starting your migration now, you’ll ensure your apps remain robust, compliant, and ready for Apple’s evolving ecosystem. If you have questions or need assistance, reach out via Apple Developer Forums or share your thoughts in the community.

Happy coding…

Color Management Across Apple Frameworks

divyesh vekariya — Wed, 26 Mar 2025 04:18:49 +0000

Managing colors effectively across UIKit, SwiftUI, and Core Graphics can be challenging, but Apple provides a range of tools to ensure consistency. If you're developing an app that uses multiple frameworks, understanding color spaces, rendering differences, and best practices is crucial.

Why Color Management Matters?

Different Apple frameworks handle colors differently. If not managed properly, the same color might look slightly different in SwiftUI, UIKit, or Core Graphics, leading to inconsistencies in your UI.

Color Spaces in Apple Frameworks

Apple frameworks support multiple color spaces. The most commonly used ones are:

sRGB: Default for most UI colors, suitable for standard displays.
Display P3: A wider gamut color space used in modern Apple displays.
Generic RGB: A more flexible option but not recommended for precise UI work.
Device RGB: Depends on the display profile, which can lead to inconsistencies.

SwiftUI and UIKit Differences

SwiftUI and UIKit have subtle differences in color handling:

SwiftUI

Uses Color struct (built-in color management)
Automatically adjusts to different environments (light/dark mode, accessibility settings)
Supports Display P3 color out-of-the-box

UIKit

Uses UIColor (supports sRGB, Display P3)
Requires explicit color space conversion for consistency
Uses traitCollection to manage dynamic colors

Using Colors in Code

Here’s how you define colors in different frameworks:

SwiftUI

import SwiftUI

struct ContentView: View {
    var body: some View {
        Text("Hello, SwiftUI!")
            .foregroundColor(Color(.displayP3, red: 0.9, green: 0.2, blue: 0.3, opacity: 1.0))
    }
}

UIKit

import UIKit

let color = UIColor(displayP3Red: 0.9, green: 0.2, blue: 0.3, alpha: 1.0)

Core Graphics

import CoreGraphics
import CoreImage

let colorSpace = CGColorSpace(name: CGColorSpace.displayP3)
let color = CGColor(colorSpace: colorSpace!, components: [0.9, 0.2, 0.3, 1.0])

Best Practices for Color Consistency

Use Display P3 for modern Apple devices for richer colors.
Keep color definitions consistent across SwiftUI, UIKit, and Core Graphics.
Test colors on real devices (especially with ProMotion and True Tone displays).
Prefer Asset Catalogs for managing named colors in both SwiftUI and UIKit.
Handle Dark Mode properly by defining light/dark variations of colors.

DEV Community: divyesh vekariya

Are you a Senior iOS Developer who is seeking new opportunities ?

The Complete Senior iOS Developer Interview Guide (2026)

[Boost]

The Complete Senior iOS Developer Interview Guide (2026)

The Complete Senior iOS Developer Interview Guide (2026)

#ios #swift #devcommunity #programming #career

Building QR Code Generator and Scanner with SwiftUI

Mastering QR Code Generation & Scanning in SwiftUI

divyesh vekariya ・ Feb 23

Mastering QR Code Generation & Scanning in SwiftUI

🔲 QR codes look simple. But they’re powerful.

iOSDevelopment #SwiftUI #AVFoundation #CoreImage #SoftwareEngineering #MobileDevelopment

Is Native iOS Development with Swift Still Worth It in 2025?

Is Flutter Still the Best Choice in 2025?

Swift vs. Kotlin vs. Flutter in App Development: What to Choose? | by Rahim Ladhani | Medium

Rahim Ladhani ・ May 28, 2025 ・ nevinainfotech25.Medium

Latest iOS 26 TextKit API's

How to Build Rich Text Editor in SwiftUI

divyesh vekariya ・ Oct 6

How to Build Rich Text Editor in SwiftUI

Free GraphQL APIs You Can Use Today

1. SpaceX API

2. SWAPI (Star Wars API)

3. Rick and Morty API

4. Countries API

5. PokeAPI (GraphQL Wrapper)

6. DexAPI

7. Anilist API

8. GitHub API

iOS 19 SDK Developer Update: Prepare for UIApplicationDelegate Deprecations

Affected APIs

What Does Deprecation Mean?

Why the Shift to UISceneDelegate?

Action Plan for Developers

Example Migration

Community Discussion

Stay Ahead

Color Management Across Apple Frameworks

Why Color Management Matters?

Color Spaces in Apple Frameworks

SwiftUI and UIKit Differences

SwiftUI

UIKit

Using Colors in Code

SwiftUI

UIKit

Core Graphics

Best Practices for Color Consistency

Further Reading

Rahim Ladhani ・ May 28, 2025 ・
nevinainfotech25.Medium