Admin Panel Development for Mobile Apps

Your mobile app is live, users are registered — and suddenly you realize there's no way to block an account without a direct SQL query, change a banner without a deploy, or view statistics without Excel. Our team develops admin panels that solve these problems. With 5+ years of experience and over 20 completed projects, we create interfaces to manage users, content, push notifications, and analytics without a single SQL query. Here we break down the key components and technical solutions we apply.

Admin Panel Modules

Here are the typical modules we include:

Technical Stack and Architecture

Backend API for Admin

The admin panel works with the same backend services as the mobile app, but via a separate set of endpoints with broader permissions. Important: do not grant mobile clients admin rights using the same token. The admin API requires separate authentication (separate OAuth2 client_id or separate service) and separate middleware with role checking.

On Laravel, we use spatie/laravel-permission for roles and permissions. Roles: super_admin, content_moderator, support. Every admin action is logged in activity_log (package spatie/laravel-activitylog): who, when, what changed, old and new values. Without this log, incident investigation is impossible.

On Node.js/NestJS — @nestjs/passport + casl for ABAC. For audit logging — middleware that writes to a separate table or sends events to Kafka/RabbitMQ.

Which Frontend to Choose for the Admin Panel?

We compare three main approaches:

For most mobile products, we recommend React + Tanstack Table + React Query + Shadcn/ui: a custom solution is 2-3 times more flexible than low-code, while development speed is comparable. Moreover, a custom solution pays off 2 times faster than low-code when there are more than 10 entities.

Configuring Push Notifications from the Panel

Integration with Firebase Cloud Messaging via Admin SDK. Firebase Admin SDK allows sending notifications in batches of up to 500 tokens. The panel lets you select a user segment (by registration date, platform, activity, custom tags), write text and title, schedule sending, or send immediately.

Recently on a project with 500k DAU, we implemented segment-based sending: we needed to send a promo only to iOS users who hadn't logged in for over 7 days. The panel built the segment in 2 clicks, batch sending via sendMulticast processed 200k tokens in 30 seconds. Result: 15% conversion to orders.

Implementation steps:

1. Install Firebase Admin SDK on the backend.
2. Implement send endpoint (use sendMulticast with batches of 500 tokens for large segments).
3. Process the result: successCount and failureCount saved to history.
4. Automatically remove expired tokens (exception UNREGISTERED).

On the backend: FirebaseAdmin.messaging().sendMulticast() for group sending. The send result — BatchResponse — is saved for history.

Why Feature Flags Save Time

The simplest implementation: a table feature_flags (key, enabled, rollout_percentage, updated_at). The mobile app requests flags on startup and caches them. The panel allows toggling flags and setting audience percentage. This cuts the time to roll out a new feature to minutes instead of a deploy — for example, A/B testing a new onboarding: 50% of users get the new version, we collect metrics, and decide in a day. Without flags, we'd need a separate build.

For more complex scenarios — Firebase Remote Config or LaunchDarkly. Remote Config is free and sufficient for 90% of tasks: panel in Firebase Console, SDK on mobile with fetch() + activate(), minimumFetchInterval in seconds to control request frequency.

How to Ensure Admin Panel Security

• Separate domain or subdomain (only admin.yourapp.com, not yourapp.com/admin)
• MFA mandatory for all admin accounts
• IP whitelist if the team works from fixed offices
• Rate limiting on all endpoints
• HTTPS only, HSTS
• Sessions with short TTL (8 hours), auto-logout on inactivity
• Content Security Policy headers

What's Included in the Work and Timelines

• API documentation: full description of endpoints, models, and access rights
• Source code: private repository with CI/CD
• Deployment instructions: step-by-step guide for DevOps
• Team training: webinar or personal consultation on administration
• Support: warranty maintenance for 3 months after delivery

Timelines: from 1 week to 3 months. A basic CRUD panel with user management and push — 1–2 weeks. A full system with analytics, feature flags, complex role model, and audit log — 1–3 months.

We guarantee stable operation and transparency at every stage. Interested? Contact us for a consultation — we'll evaluate your project and select the optimal solution for your tasks.

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.