Mobile app design services for startups shipping on iOS and Android

I'm Maniruzzaman Jubayer, and I offer mobile app design services for startups, covering iOS and Android from the first user interview to the last App Store screenshot. Working with founders in Europe, the US, the Gulf and Asia, I can build the app in React Native or Flutter, or hand your own developers a design system and tested prototypes for Swift, Kotlin, Flutter or React Native.

Free 30 min intro call · iOS and Android · One fixed quote

Founders shipping iOS and Android apps work with me

Raised by my clients
$30M+
Monthly visits on client platforms
10M+
Client satisfaction in project reviews
90%
Companies helped
50+
Years designing and building mobile apps
6+
Behance features
20+

Trusted by teams at

  • boon
  • Asendia AI
  • sitecove
  • mergepoint.ai
  • Parfait Art Logistics
  • oneclick

Designed and built by Maniruzzaman Jubayer, design engineer.

The mobile app problems founders bring me

Most apps that reach me have at least one of these. Here is how I fix each one.

The app feels like a website in a frame

Tab bars, back gestures and sheets that ignore Apple's Human Interface Guidelines and Material Design 3 make an app feel foreign on both phones.

I design each platform's navigation, controls and type to its own conventions, then share everything that can be shared in one system.

People install it, then never open it again

A long tour, a sign-up wall and four permission prompts before anything useful happens give new users every reason to leave.

I redesign the first session around one early win, and ask for location, camera or notifications only when a feature actually needs them.

It falls apart on a weak signal

Spinners that never stop, forms that lose what was typed, and payments that may or may not have gone through.

I design the offline, slow and failed states for every key screen, so people always know what saved, what is waiting and what to retry.

App review keeps saying no

A missing demo account, no way to delete an account inside the app, or a vague permission message can each send a build back and push the launch.

I check the design against Apple's App Review Guidelines and Google Play's policies before you submit, not after the first rejection.

Mobile app case studies

An AI healthcare app for finding a doctor and booking, an iOS app that redesigns a room from one photo, and a delivery app built around live tracking, each designed by me.

CareUp: An AI healthcare app for finding a doctor and booking

Product design · Healthcare

CareUp

A mobile healthcare app, from user research and wireframes to the final UI.

Read the case study →
RoomMind AI: An iOS app that redesigns a room from one photo

Product design · AI

RoomMind AI

Photograph a room, pick a style, get an AI redesign in seconds. The full iOS app, from user flow to final UI.

Read the case study →
Shipora: A delivery app built around live tracking

Product design · Logistics

Shipora

Ordering, tracking and on-time delivery in one mobile app, with the research and persona work behind it.

Read the case study →

Is your app losing people before they reach the first useful screen?

Book an intro call

iOS and Android app design, from first sketch to store listing

Six pieces of work in one engagement, each one something your developers or your store listing will actually use.

Interviews, a read of your analytics and store reviews, and every core journey mapped screen by screen, including sign-in, onboarding and the paths that end in a payment or a booking.

Every screen and state for both platforms, with system bars, safe areas and the Android back gesture accounted for, and edge-to-edge layouts, which Android applies by default to apps targeting Android 15 or later.

Components, tokens and type styles that scale with Dynamic Type and Android font size, light and dark themes, and touch targets of 44 by 44 points on iOS and at least 48 by 48 dp on Android.

Clickable prototypes that people try on their own devices, so problems with reach, wording and flow show up before a single sprint is spent building the wrong thing.

Screenshot sets and listing visuals sized for each store, plus the wording for every permission prompt and the notes your reviewer at Apple or Google will read.

Annotated specs, exported assets and tokens that map onto SwiftUI, Jetpack Compose, Flutter or React Native components. I can also build the app itself in React Native or Flutter, and the web app or admin panel beside it in React and Next.js; see development.

From first call to app store, in four steps

The same four steps for every app, with platform rules and store review planned in from the first week.

  1. 01

    A free 30 minute intro call

    Show me the app, the prototype or the idea on your own phone. We talk about who uses it, which platform comes first and what is blocking launch, and I tell you plainly whether I am the right fit.

  2. 02

    A written scope and one fixed quote

    The flows, platforms, devices and deliverables in writing, with one fixed quote for the whole project before anything starts. Nothing is billed by the hour and there is no retainer.

  3. 03

    Design and test sprints

    Weekly sprints in shared Figma, a written update in Slack every 48 hours and a review call each week. Prototypes go in front of real users on real phones before screens are signed off.

  4. 04

    Handoff, build and submission

    A walkthrough of the design system with whoever builds it, my React Native or Flutter developers or your own team, quick answers during the build, and store screenshots and review notes ready on the day your build goes to Apple and Google.

Working with me on your app

Platforms
iPhone and iPad, Android phones and tablets, and the web app or admin panel that sits beside them
Clock
UTC+6 all year, so when Europe or the US changes its clocks, only one side of the call moves
Working week
Sunday to Thursday, as Friday and Saturday are the weekend in Bangladesh
Testing
prototypes checked on real iPhones and Android phones, including the mid-range models many of your users carry
Ways to talk
Google Meet for reviews, Slack in between, and Figma comments on the screens themselves

Industries I design mobile apps for

Six sectors where the phone is the product, and what each one asks of design.

  • Payments and wallets: a screen from a product I designed

    Payments and wallets

    Sending, receiving and topping up in a few taps, with identity checks that feel quick, a clear status for every transfer and a receipt people can trust when the signal drops halfway.

    My fintech work →
  • Personal finance and wealth: a screen from a product I designed

    Personal finance and wealth

    Balances, budgets and investments read on a small screen in seconds. Charts need plain labels, AI insights need their reasons shown, and nothing private should ever appear in a notification.

    My fintech work →
  • Healthcare and telehealth: a screen from a product I designed

    Healthcare and telehealth

    Finding a doctor, booking a slot and joining a call, often for someone unwell or older. Large text, VoiceOver and TalkBack support and calm consent screens matter more here than anywhere.

    My healthcare work →
  • AI consumer apps: a screen from a product I designed

    AI consumer apps

    Camera-first flows where people share a photo and wait for a result. The app has to set expectations, show progress honestly and make a poor result easy to refine. My guide to shipping AI features people trust sets out how.

    My ai products work →
  • Delivery and logistics: a screen from a product I designed

    Delivery and logistics

    Live tracking for customers, and one-handed screens for couriers working outdoors in bright sun on patchy networks. Every status change has to read at a glance, and every notification has to be worth opening.

    My logistics work →
  • Agriculture and field work: a screen from a product I designed

    Agriculture and field work

    Apps used on farms and sites far from good coverage, where data has to save on the phone and sync later, and controls have to be large enough for working hands in daylight.

How I work with your app team, wherever you are

You see the work as it happens, in your own hours, without having to chase anyone for it.

My day
Your day

7hours of your working day overlap mine

  • You work with me directly

    Reviews are with me, the person drawing your screens, and your developers ask me their questions directly. There is no account manager relaying messages in between.

  • Overlap with your day

    Gulf and Asian teams share most of my working day, and Europe shares its morning with my afternoon. For founders in the US, I keep evening calls, 7 to 10 pm my time, which is your morning.

  • Written, tracked and testable

    Shared Figma from the first day, a Slack update every 48 hours, a call each week, and prototype links you can open on your own phone and pass round your team between reviews.

  • I know both platforms' rules

    Apple's Human Interface Guidelines and App Review Guidelines, Material Design 3 and Google Play policy, WCAG 2.2 and the accessibility law in your market, designed into the screens rather than checked at the end.

Me, an in-house hire or a freelancer: an honest comparison

Where each option wins for a startup building its app, including the row where hiring wins.

Compare with
With me6 of 7
In-house hire1 of 7
What you getWith meIn-house hireFreelancer
A senior designer who knows both iOS and Android conventionsYesSometimesSometimes
Starts this month, without a hiring roundYesNoYes
Usability testing on real phones built into the planYesSometimesNo
Store screenshots and review readiness includedYesSometimesSometimes
The app, its web app and admin panel built by the same personYesNoNo
In your office and your stand-ups every dayNoYesNo
Cost agreed in writing before work startsYesNoSometimes

Who I help with app design for startups and growing products

Four kinds of team I work with most, across Europe, the US, the Gulf and Asia.

Founders before the first release

Pre-seed and seed teams with an idea, a prototype or a no-code test, who need the first version designed properly for both stores before the engineering budget is spent.

Live apps with a retention problem

Apps whose reviews mention confusion, lost data on slow networks or a sign-up nobody finishes. I audit the app, fix the flows that cost you most first, and redesign the rest in stages.

Web products adding an app

SaaS and fintech teams whose customers now expect an app. I bring the product's logic to the phone without shrinking the desktop, as part of my wider product design work, on one shared design system.

Apps launching in several markets

Teams releasing in Europe, the US, the Gulf and Asia at once, with right to left Arabic layouts, several languages, local payment methods and each market's privacy and accessibility rules.

Where I work with mobile app design clients

I work remotely, with real overlap in your working day.

  • Dubai

    Mobile app design and development in Dubai: iOS and Android apps in Arabic and English, with UAE PASS sign-in, local payments and store review planned in.

    How I work with Dubai teams →
  • Riyadh

    Mobile app design and development in Riyadh: Arabic-first iOS and Android apps designed and built in React Native or Flutter, with Nafath, mada and PDPL consent planned in.

    How I work with Riyadh teams →
  • Abu Dhabi

    Mobile app development in Abu Dhabi: iOS and Android apps designed and coded by one person, in Arabic and English, with UAE PASS and store review planned from the start.

    How I work with Abu Dhabi teams →

An app rarely ships on its own. These usually come with it.

What founders say about working with me on their apps

“The final product exemplified Muhammed’s profound comprehension of UI design principles, presenting a visually captivating experience that was both seamless and intuitive for users.”
Youssef RzikiClient, oil and gas trade
“I highly recommend Jubayer for any design project. He quickly grasps complex concepts, excels in standard design practices, and responds promptly.”
Abhishek NaleProduct lead, Strell

Guides for app founders

Practical writing on AI features, interface type and getting the product right.

Free tools for this

Small jobs from this kind of work, done in your browser. Free, no sign-up, and nothing you add leaves your device.

MVP timeline calculator

Pick a product type and its features to see how many weeks an MVP takes, phase by phase.

Open the tool: MVP timeline calculator →

Colour contrast grid

Every pair in a palette scored against WCAG 2.2, shown in real UI, with the nearest passing colour.

Open the tool: Colour contrast grid →

SVG to JSX

Optimise an SVG with SVGO and turn it into a React or React Native component, a data URI or CSS.

Open the tool: SVG to JSX →

Mobile app design services: frequently asked questions

What founders usually ask me before an app project starts.

Ask me on a free call
  • Not entirely. I build one set of flows and one design system, then adapt navigation, controls, type and gestures to each platform, following Apple's Human Interface Guidelines on iOS and Material Design 3 on Android. Most screens share their layout, while tab bars, back behaviour, sheets, date pickers and system dialogs differ. You avoid paying for two designs, and neither app feels borrowed from the other.
  • Yes. I design for whatever your team builds with: Swift and SwiftUI, Kotlin and Jetpack Compose, React Native or Flutter. For cross-platform frameworks, I set up components and tokens that map one to one onto the coded library, and mark where a screen should behave differently on each platform. I can build it in React Native or Flutter, or your developers can, and I add the web front end in React and Next.js.
  • It depends on the number of core flows, whether you launch on one platform or both, the user roles, and how much research and testing the app needs. After a free 30 minute intro call I write a scope and give you one fixed quote for the whole project, so the number is settled before work begins. Nothing is billed by the hour, and there is no retainer.
  • No designer can promise approval, but I remove the usual design reasons for rejection. I check screens against Apple's App Review Guidelines and Google Play's policies: account deletion inside the app if it offers sign-up, clear permission messages, a demo account for reviewers, and an honest Data safety section. Your developers handle technical rules, such as Google Play's rule that new apps and updates target Android 16 from 31 August 2026.
  • Yes, as part of the store listing work. Apple accepts one to 10 screenshots per device size and Google Play up to 8 per device type, and Apple's guidelines ask that they show the app in use rather than a splash or login screen. I plan the set as a short story of what the app does, sized and exported for each store.
  • From the first component, not in a final audit. I design to WCAG 2.2 AA, with touch targets at each platform's recommended size, text that scales with Dynamic Type and Android font settings, labels for VoiceOver and TalkBack, no action that only works by dragging, and contrast checked in light and dark themes. In the EU, the European Accessibility Act has covered most banking and e-commerce apps since 28 June 2025.
  • Yes, and it is far easier to plan from the start. For each key screen I decide what is kept on the phone, what happens when the connection drops mid-task, and how the app shows what has synced, what is waiting and what failed. Google describes an offline-first app as one that keeps its core functions working without the internet; I design the states that make that visible and trustworthy.
  • When people reach the feature that needs them, not at launch. Apple advises waiting until someone uses a feature that requires access, and on Android 13 and later notifications need a runtime permission too. I design a short explanation in context, write the permission message in plain words, and give people a way forward if they say no, such as typing an address instead of sharing their location.
  • Between the two. I'm one senior designer, so you get a freelancer's direct line to the person responsible, and for larger builds I bring in developers I have worked with for years. You talk to me, the person drawing your screens, never to an account manager. I work remotely, not from a local office in your city.
Sources and references (25)
  1. Apple, Human Interface Guidelines: Accessibility (default control size 44x44 pt on iOS, minimum 28x28 pt; text enlargement to at least 200 percent; VoiceOver), page changes dated 9 June 2025, read 4 October 2026: developer.apple.com
  2. Apple, Human Interface Guidelines: Typography (Dynamic Type lets people adjust text size systemwide), read 4 October 2026: developer.apple.com
  3. Apple, Human Interface Guidelines: Privacy (request permission when a feature needs it, avoid launch-time requests, clear purpose strings), read 4 October 2026: developer.apple.com
  4. Apple, Human Interface Guidelines: Onboarding (fast, optional onboarding; permission requests in context), read 4 October 2026: developer.apple.com
  5. Apple, Human Interface Guidelines: Notifications (no sensitive or personal information in notifications; no repeat notifications), read 4 October 2026: developer.apple.com
  6. Apple, App Review Guidelines (2.1 demo account for apps with a login; 2.3.3 screenshots show the app in use; 4.5.4 push notifications; 5.1.1(iv) offer alternatives such as entering an address when location is declined; 5.1.1(v) in-app account deletion), last updated 8 June 2026: developer.apple.com
  7. Apple, App Store Connect Help: Screenshot specifications (one to 10 screenshots in .jpeg, .jpg or .png), read 4 October 2026: developer.apple.com
  8. Google, Material Design 3: Accessibility designing, structure, read 4 October 2026: m3.material.io
  9. Android Developers, Make apps more accessible (touch targets of at least 48dp x 48dp), read 4 October 2026: developer.android.com
  10. Android Developers, Design for Android: Accessibility (touch targets at least 48 dp; TalkBack screen reader; do not rely on gestures alone), last updated 8 May 2023: developer.android.com
  11. Google, Accessibility Scanner Help: Touch target size (48x48dp, about 9 mm, separated by 8dp), read 4 October 2026: support.google.com
  12. Android Developers, Behaviour changes: apps targeting Android 15 (edge-to-edge by default when targeting API level 35), read 4 October 2026: developer.android.com
  13. Android Developers, Notification runtime permission (POST_NOTIFICATIONS on Android 13, API level 33, and higher; ask in context), last updated 1 October 2026: developer.android.com
  14. Android Developers, Build an offline-first app (core functionality without access to the internet), last updated 13 May 2026: developer.android.com
  15. Google Play Console Help, Target API level requirements (from 31 August 2026 new apps and app updates must target Android 16, API level 36), read 4 October 2026: support.google.com
  16. Google Play Console Help, Add preview assets to showcase your app (up to 8 screenshots for each supported device type), read 4 October 2026: support.google.com
  17. Google Play Console Help, Understanding Google Play's app account deletion requirements (in-app path and a web link to request deletion), read 4 October 2026: support.google.com
  18. Google Play Console Help, Provide information for Google Play's Data safety section (all published apps complete the form), read 4 October 2026: support.google.com
  19. W3C WAI, What's new in WCAG 2.2 (Recommendation 5 October 2023; 2.5.7 Dragging Movements, 2.5.8 Target Size Minimum of 24 by 24 CSS pixels, 3.3.8 Accessible Authentication), read 4 October 2026: w3.org
  20. W3C, Web Content Accessibility Guidelines (WCAG) 2.2, current version 12 December 2024, read 4 October 2026: w3.org
  21. AccessibleEU (European Commission), A new era for inclusion begins: the EAA enters into force (from 28 June banks, e-commerce platforms and transport apps must be accessible), 27 June 2025: accessible-eu-centre.ec.europa.eu
  22. Business.gov.nl, Rules for accessibility of products and services (EAA covers websites and apps for e-commerce and consumer banking), read 4 October 2026: business.gov.nl
  23. Steven Hoober, UXmatters, How Do Users Really Hold Mobile Devices? (1,333 observations; of 780 people touching the screen, 49 percent one-handed), 18 February 2013: uxmatters.com
  24. Wikipedia, Bangladesh Standard Time (UTC+6, daylight saving cancelled in 2010), read 4 October 2026: en.wikipedia.org
  25. The Daily Star, Gazette issued on new office timings (Friday and Saturday remain weekly holidays), 5 April 2026: thedailystar.net

Let's design the app your users keep

A free 30 minute call. You leave with a clear next step, whether we work together or not.

Book a free intro call