Skip to content
Puneetpal Arneja.Start a project

iOS Developer in Fort Worth, TX for Secure and Regulated Apps

I am a senior iOS developer working with Fort Worth teams on the apps that get audited: mobile banking and fintech, healthcare, and internal enterprise tools, plus the related job of bringing an older UIKit app up to date without taking it offline. I have 13+ years in Swift, SwiftUI and UIKit, and my work includes a pharmacy and health app for Albertsons, Citi Mobile, PNC and Citizens Bank, and an internal logistics app for Apple retail. I’m based in Dallas–Fort Worth and available remote across the US or onsite in DFW.

A security-sensitive app is mostly an ordinary app with a longer list of things that must not go wrong. The sections below go through that list, so you can judge whether I know it before we talk.

Building for Bank and Fintech Security Review

Banks review mobile apps against a control list before release, and they re-review on every significant change. The controls are not secret, but they interact with each other and with Apple’s platform in ways that trip up teams doing it for the first time. The ones that come up in every review:

  • Credentials and tokens live in the Keychain with an accessibility class that matches how the app is used, never in UserDefaults or a file. Biometric authentication is tied to the Secure Enclave rather than a boolean in the app.
  • Sessions use short-lived access tokens with refresh and server-side revocation, so a stolen token has a shelf life measured in minutes and a lost phone can be cut off from the server.
  • Certificate validation is deliberate. Pinning stops some interception but turns every certificate rotation into a forced app update, so the decision is made with the operations team, not by default.
  • Sensitive screens are masked when the app moves to the background, so balances and account numbers do not appear in the app switcher or in screenshots.
  • Jailbreak and debugger detection is treated as one signal among several. It raises the bar; it does not replace server-side controls.
  • Logging has a written policy. Account numbers, tokens and personal data never reach the console, the crash reporter or analytics, and the policy is enforced in code review.
  • There is a kill switch. The server can refuse a build version, so a release with a defect can be retired without waiting for every user to update.

The full list, mapped to OWASP MASVS v2 with the testing approach for each item, is in the mobile banking security checklist. The server side has its own list, mapped to the OWASP API Security Top 10, in the Laravel API security checklist. Most mobile security problems I find in audits are actually API problems wearing an app badge.

Healthcare Apps and HealthKit

My current role is on Sincerely Health, the Albertsons pharmacy and health app. I built its HealthKit layer, which reads steps, active energy, sleep and workouts, including live Apple Watch data, and the permission flow that Apple’s Health guidelines require before any of that data is touched. Health data on iOS has rules that a general-purpose developer will not know: it cannot be used for advertising, it cannot be written to iCloud by the app, and the purpose of each read has to be stated to the user in plain language when permission is requested.

For Fort Worth healthcare teams the same disciplines from the banking list apply, with the logging rule mattering most: health data in a crash report is a reportable incident. I also build the usual clinical and pharmacy plumbing, such as secure messaging, appointment and refill flows, and document capture, with the data model agreed with your compliance owner before the first screen is built.

Enterprise and Internal Apps

Backstage, the internal logistics app Apple retail staff use to move items between stores, is the clearest example on my record of an app that never goes near the public App Store. Internal apps have their own set of concerns: distribution through a device management system rather than the store, sign-in through the company identity provider, working on a shared device that several people use in a shift, and behaving sensibly on a warehouse floor where the network drops.

Fort Worth has large employers in aviation, logistics and healthcare, and the internal apps those operations run on are rarely glamorous and usually important. If yours was built years ago and the person who understood it has left, the modernisation work below is where to start.

Modernising an Existing UIKit App

Many regulated apps are eight or ten years old, written in UIKit with a mix of storyboards and code, and still in daily use. The instinct is to rewrite. I almost always advise against it: a rewrite freezes features for a year, reintroduces bugs that were fixed long ago, and has to pass the same security review again from scratch. The approach I use instead:

  1. A mobile architecture audit first, two to three weeks, so we know where the crashes, the hidden state and the security gaps actually are.
  2. Raise the deployment target and clear the deprecation warnings, which alone removes a class of future breakage when a new iOS version ships.
  3. Build every new screen in SwiftUI, hosted inside the existing UIKit navigation with UIHostingController, so the modern code grows without a flag day.
  4. Move existing screens over one at a time, starting with the ones that are simple and frequently changed, and leave stable complex screens in UIKit until there is a business reason to touch them.
  5. Put CI, automated UI tests on the critical flows and crash monitoring in place early, so each step is verified before the next.

The code-level detail, including the interop patterns and a per-screen checklist, is in the UIKit to SwiftUI migration playbook. The service itself is described on the SwiftUI development and UIKit migration page.

Working With Fort Worth Teams

Contract work is $120–$180/hr, and I also take senior and tech lead full-time roles. For regulated work the engagement usually has a shape the compliance team will recognise:

  • NDA and, where required, a background check before any code or data is shared
  • Work on your managed hardware or inside your network when policy requires it
  • A threat model written down before the build, so the security review has something to check against
  • Findings and fixes tracked in your system, with evidence for the auditor
  • A release process that includes the security sign-off step rather than treating it as an afterthought

The same arrangement works for teams in the Mid-Cities between Dallas and Fort Worth, such as Euless, Bedford, Hurst, Arlington and Grapevine, which are an easy drive for onsite days.

The process page describes how I communicate and test on any engagement, and hire me covers current availability for contract and full-time work.

Frequently Asked Questions

Have you built iOS apps that went through bank security review?

Yes. I led the redesign of the Linking, KYC and Registration modules in Citi Mobile, and worked on the PNC and Citizens Bank mobile banking apps. Those reviews cover how credentials and tokens are stored, how the app behaves on a jailbroken device, what gets logged, how certificates are validated, and how a compromised release gets pulled. I build with those questions in mind from the first commit, because retrofitting them is slow and expensive.

What does a security-sensitive iOS build include that a normal one does not?

Keychain storage with the right accessibility class, biometric authentication tied to the Secure Enclave, short-lived tokens with refresh and revocation, certificate validation with a considered pinning strategy, masking of sensitive screens in the app switcher, jailbreak detection as one signal among several, a logging policy that keeps account data and health data out of logs and crash reports, and a server-side kill switch for old builds. The banking security checklist on this site lists each item with the OWASP MASVS control it maps to.

Can you modernise our UIKit app without rewriting it?

Yes, and I recommend against the rewrite in almost every case. New screens are built in SwiftUI and hosted inside the existing UIKit navigation through UIHostingController; existing screens move over one at a time when there is a reason to touch them. The app ships throughout. I start with an audit of the current codebase so we know which screens are safe to move first and which carry hidden state.

Do you also harden the backend API the app depends on?

Yes, for Laravel backends. Most mobile security failures are really API failures: tokens that never expire, authorisation checked in the app but not on the server, rate limits missing on login and password reset. I review the API against the OWASP API Security Top 10 alongside the app so the two are hardened together.

How long does a security and architecture audit take?

Usually two to three weeks for a single iOS app with its API. You get a written report with findings rated by severity, the fix for each, and a sequence to do them in. I can stay on to implement, or hand it to your team.

Do you work onsite in Fort Worth or remotely?

Both. I am based in Dallas–Fort Worth and can be onsite for security reviews, release planning or a full-time role, and I work remotely with teams across the US. Regulated clients sometimes need work done on managed hardware or inside their network; that works too.

Elsewhere in DFW: the Dallas page covers hiring an independent iOS engineer in general, the Plano page covers fractional mobile tech lead work, and the Frisco page covers MVPs and first versions for founders.

Building or inheriting an app that has to pass review? Talk to the engineer who would do the work.