Implementing Annotations for Elements in a Mobile App
We develop annotation systems for mobile apps — not just a chat overlay on content, but binding a comment to a specific point on an image, document, or list item. We have 5+ years of experience in this niche and have delivered over 20 projects with annotations for iOS, Android, and Flutter. Here we share the key technical solutions that ensure stability and performance.
How to Normalize Coordinates for Different Screens?
The core problem: a user taps an image on an iPhone SE with one screen size, while another views the same document on an iPad Pro in landscape. The pin must point to the same spot. The solution: store relative coordinates, not absolute pixels — x and y as a fraction of the container width and height (from 0.0 to 1.0). On rendering, multiply by the actual container size. On iOS: CGPoint(x: pin.relativeX * containerWidth, y: pin.relativeY * containerHeight). On Flutter: similarly using Positioned inside a Stack with computed left and top.
For documents with zoom, it gets more complex: you need to account for contentOffset and zoomScale of UIScrollView. We store the coordinate in content space, and when displaying, convert to screen coordinates using UIScrollView.convert(_:to:). This ensures pins don't "drift" when zooming. A typical bug: calculating in viewport coordinates instead of content. We fix it by adding scrollViewDidZoom to force positions update.
How to Implement Real-Time Annotation Synchronization?
Each pin is an object with fields: id, contentId, relativeX, relativeY, authorId, createdAt, text, resolved. The latter is important: the ability to mark a comment as resolved is a standard feature for review tools.
For synchronization between users, we use WebSocket (Socket.io or native URLSessionWebSocketTask). A new pin appears instantly for everyone viewing the same document. Optimistic update: add the pin to local state immediately, send the request, rollback on error. For offline scenarios: Core Data or SQLite with a pendingSync flag. On reconnection — batch sync via REST.
Comparison of Coordinate Storage Approaches
| Approach |
Description |
Advantages |
Disadvantages |
| Absolute pixels |
Fixed x,y in pixels |
Simple implementation |
Doesn't work on different screens |
| Relative coordinates |
x,y as fraction of width/height |
Scalable across screens |
Requires normalization |
| Content space coordinates |
Internal document coordinate system |
Correct under zoom and scroll |
More complex conversion |
Relative coordinates with content space is the optimal choice. Pin clustering reduces UI load by 10x compared to rendering all markers when there are 50+ points.
Pin UI Component
A pin on screen is a UIView (or View in SwiftUI / widget in Flutter) with absolute positioning. Some practical details:
- Pins must not overflow the container. When
relativeX > 0.95, push the tooltip to the left edge; when < 0.05, to the right. Similarly vertically. Simple logic, but without it the tooltip goes off-screen.
- If there are many pins (50+), rendering all at once is not advisable. Use clustering: at small zoom, group nearby pins into a cluster with a count. Expand on zoom. On iOS —
MKClusterAnnotation as a pattern (even if not working with maps). On Flutter — manual clustering via quadtree or the library flutter_map_marker_cluster.
Typical Implementation Mistakes
- Storing coordinates in viewport pixels — pins "drift" on zoom.
- Ignoring offset and zoomScale of ScrollView — pin position mismatches after scrolling.
- No optimistic UI — user waits for server response.
- Rendering all pins at once when 100+ — FPS drops.
- Deep threads (more than 2 levels) — inconvenient on mobile.
Comment Thread
A single pin can have multiple replies — a thread is needed. We implement via parentId: root comments have parentId: null, replies reference the parent. We don't go deeper than one level of nesting in mobile UI — it's inconvenient.
The thread component opens as a bottom sheet (iOS: UISheetPresentationController with .medium and .large detents; Flutter: DraggableScrollableSheet). This doesn't cover the full screen and doesn't lose pin context.
What's Included in the Work
- Pin component with normalized coordinates and zoom support
- Add/edit comment form
- Reply thread in a bottom sheet
- "Resolved" status with visual differentiation
- REST API integration + optional WebSocket sync
- Pin clustering for large numbers
- Support for images, PDFs, arbitrary View containers
Timelines and Guarantees
Basic implementation (pins on image, no threads or sync): 2 days. Full version with threads, real-time sync, and clustering: 4–5 days. Cost is calculated individually after analyzing requirements and existing API.
Contact us to evaluate your project. We guarantee quality and adherence to deadlines. Order turnkey development — get a ready-made solution adapted to your stack.
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
| Parameter |
iOS (HIG) |
Android (Material Design 3) |
| Minimum tap target |
44×44 pt |
48×48 dp |
| Safe area |
safeAreaLayoutGuide / safeAreaPadding |
Insets in WindowInsets |
| Back gesture |
Swipe from left edge |
System back gesture (Android 10+) |
| Color scheme |
System dark/light |
Dynamic Color from wallpaper |
| Typography |
San Francisco (Dynamic Type) |
Roboto (Material Type Scale) |
| Haptic feedback |
UIImpactFeedbackGenerator |
HapticFeedbackConstants (Compose) |
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:
| Deliverable |
Description |
| User flows and wireframes |
Screen structure and user paths |
| Design system |
Design tokens, components, Style Dictionary for export |
| UI layouts (Figma) |
All screens following platform guidelines |
| Interactive prototype |
Prototype with variables and animations |
| Development specification |
Zeplin / Figma Dev Mode with dimensions, margins, states |
| Maintenance guide |
Recommendations for adding new screens and components |
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:
| Scope |
Timeline |
| Redesign of 3–5 screens |
1–2 weeks |
| MVP (10–15 screens) |
3–5 weeks |
| Full product (30+ screens) |
6–10 weeks |
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.
