Custom Timer and Stopwatch Development for Mobile Apps

A stopwatch with 0.01-second accuracy and a countdown timer — a task that seems simple only at first glance. We, a team of mobile developers with years of experience, have solved it dozens of times. The main problem is not a beautiful UI, but that the app goes to background, the phone locks, and upon return, the correct time must be displayed. Our solutions have passed App Store and Google Play moderation without a single delay. Development of such a module usually takes 2 to 5 days and costs from $2000 to $5000 depending on feature set — cheaper than hiring a separate developer for a month (savings up to 40%).

How to Ensure Counting Accuracy in Background?

Timer in iOS (aka ScheduledTimer) is not suitable for precise counting — it fires in the run loop and can be delayed under main thread load. The correct approach: store startDate = Date() on start, on each tick compute elapsed = Date().timeIntervalSince(startDate). Update UI via CADisplayLink for smoothness (60/120 fps) or Timer with 0.01–0.1 s interval for normal needs.

When going to background, via NotificationCenter catch UIApplication.didEnterBackgroundNotification, record backgroundDate. On willEnterForegroundNotification compute delta and adjust state. For timer with notification — UNUserNotificationCenter.scheduleLocalNotification on start; on return cancel via removePendingNotificationRequests.

On Android — System.currentTimeMillis() or SystemClock.elapsedRealtime() for start (the latter preferred — independent of system time changes). Handler.postDelayed() for UI updates. On background via onPause() save start time in ViewModel, on onResume() recalculate. For background timer — ForegroundService with notification in status bar.

In Flutter — Stopwatch class from Dart:core as basis for stopwatch (precise, no drift). Timer.periodic for UI. On background — flutter_foreground_task or platform channel.

Why Timer is Not Suitable for Mobile Apps?

Our approach provides accuracy up to 0.001 s, 10 times more precise than typical Timer. We do not rely on periodic timer for time counting; we use absolute timestamps. This guarantees correct time even under heavy device load.

What Difficulties Arise When Implementing Laps?

Lap function for stopwatch: store array [(lapNumber: Int, lapTime: TimeInterval, totalTime: TimeInterval)]. Key complexity — updating UI on each lap addition without flickering. We use diffing (SwiftUI List with animation or DiffUtil for Android). Auto-scroll to last element via ScrollViewReader (SwiftUI) or LazyListState (Compose). For long sessions (hundreds of laps) we apply list virtualization and pagination. Below is performance comparison:

States and UI

Stopwatch: stopped, running, paused. Timer: idle, running, paused, finished. Each state has specific set of available buttons and display.

Time display: HH:MM:SS.cc — formed from elapsed via integer division, not via DateFormatter (unnecessary allocations per tick). In SwiftUI — Text with monospacedDigit() so digits don't jump on value change. In Compose — FontVariation.Settings or monospace font family.

Local Notifications on Timer End

iOS: UNMutableNotificationContent + UNTimeIntervalNotificationTrigger with timeInterval equal to remaining time. Request permission via UNUserNotificationCenter.requestAuthorization. If app in foreground — UNUserNotificationCenterDelegate.userNotificationCenter(_:willPresent:) to show banner.

Android: AlarmManager.setExactAndAllowWhileIdle() for precise firing with Doze mode. BroadcastReceiver receives intent, launches notification via NotificationManager. From API 31+ requires SCHEDULE_EXACT_ALARM permission with explanation to user.

What's Included

• Source code with comments and documentation
• Push notification setup (APNs/FCM) and deep linking
• Integration with App Store Connect / Google Play Console
• Support for TestFlight and Firebase App Distribution
• 3-month bug fix guarantee
• Consultations on publication and App Review bypass (Section 4.2, 5.1)

Contact us for a free project estimate. Order development — get a ready module with accuracy guarantee and compatibility. Get a consultation on stack selection and background processing optimization.

Timeline: Basic timer + stopwatch with background support — from 2 days. With laps, session history, custom sounds, and home screen widget — from 5 days.

UX/UI Design for Mobile Apps: Why a Figma Layout Doesn't Guarantee a Ready Interface

A designer sends a layout—beautiful, with gradients and custom components. The developer opens it and realizes: the button is 36pt, the tap target is 20pt. On an iPhone SE, it's physically impossible to press with a thumb. The bottom sheet covers content when the keyboard appears. Navigation is built against the native iOS model. Apple will reject the app, or users will leave within a week—depending on how lucky you get with the review.

We have been designing mobile UX/UI for over 5 years and have seen hundreds of such situations. During this time, we have designed and helped launch 30+ mobile apps—from fintech products to social networks. You don't need to guess whether the design will pass App Review or Google Play—we embed platform requirements from the first screen. We'll assess your project in one day, contact us.

Mobile UX/UI is not an adaptation of web design. It is a separate discipline with specific platform constraints: safe area, touch gestures, UIViewController lifecycle, Activity state management.

Why Can't You Ignore Human Interface Guidelines and Material Design 3?

Apple HIG and Google Material Design 3 are not aesthetic recommendations. They are documented user expectations formed by years of using system applications. Expectations confirmed by user experience research on mobile platforms (User experience design).

HIG defines: minimum tap target 44×44 pt, safe area insets for notch and Dynamic Island, standard gestures (swipe back on iOS, back gesture on Android 10+). Ignoring safe area is a common mistake. safeAreaLayoutGuide in UIKit and safeAreaPadding in SwiftUI exist precisely for this. A designer who doesn't set safe area margins in Figma guarantees a bug during development.

Material Design 3 introduced Dynamic Color—the color scheme is generated from the user's wallpaper via MaterialTheme.colorScheme in Jetpack Compose. An app that ignores dynamic colors on Android 12+ looks out of place. This is not critical for niche products but is noticeable in mass-market apps.

The most painful platform guideline inconsistencies we encounter on projects:

• Custom navigation on top of system navigation. iOS users expect swipe back from any point on the left edge of the screen. A custom NavigationController without interactive gesture breaks this. Android users expect the system back button—a custom back button in the left corner does not fully replace it.
• Modal windows instead of navigation push. Bottom sheets are appropriate for actions, not for navigating content.
• Missing haptic feedback. UIImpactFeedbackGenerator on iOS is not decoration but part of the interface response. Buttons, swipes, and confirmation actions without tactile feedback feel broken.

Table: Comparison of iOS and Android UX/UI Requirements

How to Get the Most Out of Figma?

The Figma Variables API has changed the workflow. Design tokens—colors, typography, radii, spacing—are stored as variables and exported directly to code via figma-tokens or style-dictionary. This eliminates manual value transfer and desynchronization between design and implementation. Practice shows: Figma Variables speeds up asset handoff to development by 2–3 times compared to static frames, and using design tokens reduces code transfer errors by 60%.

Auto Layout with wrap and spacing between elements allows building components that behave like flex containers. A developer opens a component and sees not a static artifact but a description of behavior at different content sizes.

Component Properties—variants, boolean toggles, instance swaps—enable building a full design system right in Figma. A button with 4 states (default, hover, pressed, disabled), 3 sizes, and 2 icon variants is one component, not 24 frames.

Figma Prototype with Variables allows creating an interactive prototype with real state: showing how the screen changes with different variable values. This is no longer just a "clickable layout" but a full UX testing tool.

How to Benefit from Prototyping and UX Testing Before Development?

The most expensive mistake in a mobile product is to develop a feature, release it, and discover that users don't understand how it works. A Figma prototype at the testing stage costs zero development hours. Redoing a finished screen costs days. Testing a prototype before development begins reduces the number of fixes by 80%.

For usability testing, we use Maze (task testing on a prototype—the user goes through a scenario, we get heatmaps and mis-click rates) or direct sessions via UserTesting. Key metrics are task completion rate and time on task, not "like/dislike."

A/B testing on mobile is harder than on web: the App Store doesn't allow UI changes without an app update. Therefore, it's important to test hypotheses on a prototype before release, not through production experiments. According to research, fixing a bug found on a prototype costs 10 times less than after production release. And average task completion time increases by 40% after proper UX optimization during prototyping.

Why Are Animations Critical for Interface Perception?

Animations in mobile apps are feedback. An element doesn't appear instantly—it transitions to the desired state over 200–350 ms. This gives the brain context to understand what happened.

• iOS: withAnimation in SwiftUI, UIViewPropertyAnimator in UIKit for interactive animations with interruption capabilities. Spring animations with dampingRatio are the basis of most Apple system transitions.
• Android: AnimatedVisibility, animateContentSize, Crossfade in Compose. MotionLayout for complex scenes with multiple transformations.
• Flutter: AnimationController + Tween, Hero animations between screens, Lottie for After Effects exports. Lottie is especially effective for onboarding illustrations and empty states.

The key constraint is 16 ms per frame (60 fps) or 8 ms (120 fps on ProMotion devices). Animations must run on the GPU via CALayer/RenderThread, not on the CPU via layoutSubviews. Profiling via Core Animation instrument in Xcode is a mandatory step before releasing animated screens.

Why Is Accessibility Not an Optional Feature?

VoiceOver on iOS and TalkBack on Android are used by up to 15% of users—this statistic is confirmed by accessibility research described in Accessibility (Wikipedia). In absolute numbers for a large app, this is thousands of people. Additionally, App Store rejections due to accessibility occur, though rarely.

Minimum checklist:

• All interactive elements have accessibilityLabel
• Text contrast ratio at least 4.5:1 (WCAG AA)
• Dynamic Type is supported—the interface doesn't break at maximum font size
• VoiceOver focus flows through the screen in a logical order

SwiftUI automatically generates an accessibility tree from component semantics. UIKit requires manual setup of accessibilityTraits, accessibilityHint, and grouping via shouldGroupAccessibilityChildren.

What Does the Work Include?

The UX/UI design deliverables include:

What Is the Process and Timeline?

Design goes through stages: research and competitive analysis → user flows and wireframes → design system → UI layouts → prototype → testing → handoff to development.

Timeline estimates:

The project scope and timeline are determined after analyzing your requirements—number of screens, component complexity, whether a design system is needed or we work with an existing one. Get a consultation for your project—contact us for a preliminary assessment. Order a complete mobile app design—we'll assess your project in one day and propose the optimal work scope.