iOS Tab Bar Navigation Development: Customization & Best Practices

Introduction

iOS Tab Bar navigation development is one of our core competencies. When a project with tab bar navigation comes to us, we start with the system component UITabBarController. Apple recommends it for applications with two to five equal-level sections. It seems simple: drag a controller, configure tabs — done. But nuances appear immediately when you need a custom appearance, a badge with a dynamic counter, or specific behavior on a repeated tap on an active tab. As certified specialists with 7 years of experience, we have implemented tab bar navigation in dozens of projects, from news apps to banking clients. We've faced each typical mistake and now guarantee that your tab bar will pass App Store review on the first try. The cost of basic tab bar setup starts from $30 to $90.

Typical Challenges

Custom appearance setup. Since iOS 15, Apple changed the customization system — UITabBar.appearance() no longer works for some parameters. The correct approach now is UITabBarAppearance + UITabBarItemAppearance. If you don't account for this, on iOS 15+ the tab bar gets a white or gray background instead of custom, making the app look broken:

let appearance = UITabBarAppearance()
appearance.configureWithOpaqueBackground()
appearance.backgroundColor = .systemBackground
tabBar.standardAppearance = appearance
tabBar.scrollEdgeAppearance = appearance

This snippet sets a uniform background for both states. We always include it in our project template — it saves 20–30 minutes of debugging on a new SDK.

Badge counters. tabBarItem.badgeValue = "3" works out of the box, but the red circle cannot be color-changed without additional effort. Since iOS 10, there’s a badgeColor property, but it’s often overlooked. If you need a completely non-standard shape — like a square badge with rounded corners — you have to create a custom overlay on top of the tab icon. Comparison of approaches:

For 90% of scenarios, badgeColor is enough. We use a custom view only when we need to animate the badge (e.g., pulsation) — that happens once every five projects.

Repeated tap on an active tab. By default, nothing happens. The user expects the list to scroll to the top. Implementation via UITabBarControllerDelegate:

func tabBarController(_ tabBarController: UITabBarController, didSelect viewController: UIViewController) {
    guard let nav = viewController as? UINavigationController,
          let top = nav.topViewController,
          let scroll = top.view.subviews.first(where: { $0 is UIScrollView }) as? UIScrollView else { return }
    scroll.setContentOffset(.zero, animated: true)
}

This code is a universal solution. We've added it to our component library and use it in every project. It saves 30 minutes on integration. The ready-made solution works 5 times faster than writing your own from scratch.

Hiding the tab bar on scroll is another common request. It's implemented by observing the contentOffset of a UIScrollView. We hide the tab bar with animation synchronized with the content to avoid jerking. This pattern is described in Apple's HIG documentation.

How to Set Up Custom Tab Bar Appearance on iOS 15+?

On iOS 15–17, direct setting of tintColor and barTintColor stopped working. Instead, use UITabBarAppearance. Follow three steps:

1. Create a UITabBarAppearance.
2. Set backgroundColor or backgroundEffect.
3. Assign to standardAppearance and scrollEdgeAppearance.

Comparison with iOS 14: On iOS 14, you could get away with a single line tabBar.barTintColor = ..., now it's 3 times more code, but the flexibility is higher — you can set different styles for normal state and when scrolling. We always configure both to avoid a white background on iOS 15+.

Why Doesn't a Repeated Tap on a Tab Scroll to the Top?

This is a known issue: UITabBarController does not trigger scroll-to-top by default. The reason is that Apple left this logic to the developer. We solve it via the delegate as shown above. Moreover, if a tab contains multiple scroll views (e.g., Carousel + list), you need to determine which one to scroll. We use first(where:) — for standard hierarchies this is sufficient.

SwiftUI

In SwiftUI, we use TabView with the .tabItem modifier. With iOS 18, a new Tab type and sidebar support for iPad appeared. However, for complex custom animations or badges with dynamic updates, TabView still falls short. In such cases, we wrap UITabBarController via UIViewControllerRepresentable. This gives full control without performance loss — only 40–50 lines of code.

What's Included in the Work

• Setting up UITabBarController or TabView with the required number of tabs.
• Custom appearance using UITabBarAppearance considering iOS 15+.
• Badge counters updating from notification service (APNs/FCM).
• Scroll to top on repeated tab tap.
• Hiding the tab bar on scroll (optional).
• Deep linking configuration for each tab.
• iPad adaptation: tab bar can be replaced with split view.

Time Estimates

Order iOS Tab Bar navigation development with our help. Get a consultation and accurate project estimate — just contact us with a description of the functionality. Reduce development time by 30% using ready-made components.

Why is Native iOS Development the Best Choice for Complex Apps

The app crashes on cold start — EXC_BAD_ACCESS at the moment of initializing a singleton that accesses another singleton that hasn't been initialized yet. Or: a ViewController leaks memory because a closure captures self without [weak self], and that ViewController hangs in memory two transitions after the user left it. These are not hypothetical scenarios — they are the two most common classes of problems on iOS projects that come to us after another team.

We have been doing iOS development for over 5 years, delivered 40+ projects of varying complexity — from startups to enterprise solutions with millions of users. Each project undergoes 3 stages of Code Review, a custom set of UI tests (150+ test cases on average), and a mandatory run through Xcode Instruments before release.

Native iOS development with Swift means direct access to the platform. No middleware, no performance compromises, full control over what happens on every frame.

What Makes Native iOS Development on Swift the Choice for Enterprise Apps?

Native code guarantees compatibility with new Apple APIs on the day they are released, not after months of adaptation in cross-platform frameworks. For apps with latency-sensitive logic (financial terminals, medical monitors, AR navigation), this is critical. Swift with ARC and strict typing allows maintaining a crash-free rate of 99.9% with proper architecture.

SwiftUI or UIKit: What to Choose for Native iOS Development

By now, SwiftUI covers the vast majority of production tasks. But UIKit is not deprecated and will not disappear — Apple does not deprecate it but continues to add APIs. The real picture on large projects: a hybrid approach. SwiftUI for most screens, UIKit where SwiftUI hits limitations.

Which Scenarios Does SwiftUI Win Unconditionally

SwiftUI's declarative syntax reduces UI code by 3-5 times compared to UIKit. A settings screen with List, Toggle, Picker — that's 40 lines of SwiftUI versus 200 lines of UIKit with UITableViewDataSource delegates. Time savings on UI development reach 60%. Apple recommends starting new projects on SwiftUI (Human Interface Guidelines).

@State, @Binding, @ObservableObject (and with iOS 17, the @Observable macro) create a reactive link between data and UI without manual reloadData(). Changing a @State variable automatically redraws the affected part of the hierarchy. This works correctly if you understand how SwiftUI computes the diff — via Equatable and id in ForEach.

AsyncImage, NavigationStack with type-safe routing via NavigationPath, searchable, refreshable — these are ready-made patterns that UIKit requires implementing manually.

When UIKit Remains Necessary

UICollectionView with compositional layout and diffable data source — complex grids with different cell types, horizontal sections inside vertical scroll, dynamic cell sizes. SwiftUI LazyVGrid / LazyHGrid do not provide such control.

Custom transitions between screens. UIViewControllerAnimatedTransitioning and UIViewControllerInteractiveTransitioning — interactive pop gesture with partial progress, custom hero transition with precise frame control. SwiftUI matchedGeometryEffect covers some cases, but not all.

UITextView with TextKit 2. Rich text editor, custom attributes, custom rendering — TextKit 2 (available since iOS 16) switched to async layout, solving performance issues on long documents. SwiftUI TextEditor is a wrapper around UITextView without direct access to TextKit.

UIScrollView with custom behavior. scrollViewDidScroll, parallax effects, sticky headers with custom logic, pull-to-refresh with custom indicator. SwiftUI ScrollView with scrollPosition and onScrollGeometryChange (iOS 17) covers some cases, but not all.

How Do We Integrate SwiftUI and UIKit Step by Step

1. Identify screens where SwiftUI gives maximum gain (lists, forms, settings) — usually 70-80% of screens.
2. For performance-critical areas (complex collections, custom animations) leave UIKit.
3. Use UIHostingController to embed SwiftUI views into UIKit navigation stack.
4. For backward compatibility, wrap UIKit components via UIViewRepresentable.
5. Coordinator pattern (UIKit) manages navigation at the flow level, screens are implemented in SwiftUI.

One pattern we use on projects: UIKit coordinator manages navigation, while the screens themselves are in SwiftUI. The coordinator creates a UIHostingController, passes ViewModel via initializer or @EnvironmentObject, and manages transitions. This gives clean separation: SwiftUI handles UI, Coordinator handles navigation.

How async/await and Combine Work Together

Before Swift 5.5, asynchronous code on iOS was built on Combine or callback chains. With the advent of async/await and Actor, concurrency has become part of the language. On new projects we use async/await as the primary tool for network calls and business logic, and Combine for reactive UI state binding.

// Correct — @MainActor guarantees UI updates on main thread
@MainActor
class UserViewModel: ObservableObject {
    @Published var user: User?
    @Published var isLoading = false

    func loadUser(id: String) async {
        isLoading = true
        defer { isLoading = false }
        do {
            user = try await userService.fetch(id: id)
        } catch {
            // handle error
        }
    }
}

Combine remains indispensable for debouncing input, merging multiple Publishers (CombineLatest, Zip), and functional processing of value streams (map, flatMap, filter). In practice, 80% of projects use both approaches, choosing the tool for the task.

iOS App Architecture

MVVM — the basic pattern. ViewModel contains logic and @Published state, SwiftUI View subscribes via @ObservedObject or @StateObject. One rule: View knows nothing about URLSession, CoreData, UserDefaults.

Clean Architecture adds Repository and UseCase layers. UserRepository abstracts the data source (network vs cache). FetchUserUseCase contains business logic. UserViewModel calls UseCase and manages UI state.

TCA (The Composable Architecture) — a stricter pattern from Point-Free. State, Action, Reducer, Effect — everything explicit, testable, composable via Scope. Works well in large teams (5+ iOS developers) where predictability is important.

What's Included in iOS App Development

Tools Without Which No Release Is Complete

Xcode Instruments. Time Profiler shows where CPU spends time. Allocations — memory leaks and excessive allocations. Leaks — objects that are not freed. Before every release — a mandatory run.

Firebase Crashlytics. Crash-free rate, grouping by stack trace, breadcrumbs of events leading to crash. Set up in 30 minutes, provides visibility across the entire device fleet. On our projects, average crash-free rate is 99.8%.

Fastlane match. Manage certificates and provisioning profiles via an encrypted git repository. Eliminates the 'it builds locally but not on CI' issue once and for all. Saves up to 4 hours per build when signing manually.

XCTest + XCUITest. Unit tests for ViewModel and UseCase, UI tests for critical flows (onboarding, payment, authorization). On average, code coverage is 75%.

Process and Timelines

Cost is calculated individually after analyzing the technical specification and design. Typically, the first 2 weeks are spent on design, after which we finalize the timeline and budget.

Order turnkey development — we will evaluate your project in 2 business days and propose the optimal architecture. Contact us to discuss your task: we guarantee code quality, compliance with App Store Review Guidelines, and experience with projects of any scale. Get a consultation — we will help you choose the right stack and avoid common mistakes at the start.