// Service · Mobile App Development
Mobile App
Development
Apps people open every day. And don't delete after a week.
Building an app is the easy part. Building an app people love, return to, and recommend — that's the real story. The difference is in the details: performance, UX, battery life, offline sync, notifications that don't annoy. Every small detail can sink an app.
We build iOS and Android apps — from a first MVP to products running in production today, like Onit, Tory, Dividandy and Planner, shown further down this page with what we built in each. We've learned where the pitfalls are — and how to avoid them.
// Where you start
What does the app need to let the user do?
Three situations people come to us in. The first question is different in each — and it sets the scope before anyone talks technology.
- 01
A new product
There's an idea, maybe a deck, no product yet. The first question: who is the first user and what is the one action they must complete — that is the boundary of version one.
- 02
A service for existing customers
The business runs, the customers exist, and they need an easy way to order, track or get updates. The first question: which action the customer does today by phone or email will move into the app.
- 03
Connecting an existing system to mobile
There's a system — ERP, CRM, an internal tool — and staff or customers need part of it in the field. The first question: does the system have an API and who holds access; that is the biggest uncertainty factor in the scope.
// 01 · What we build
What we build
From B2C to B2B, from e-commerce to AI-powered apps. Every app — tailored to its audience.
- 01
B2C apps
For end consumers. Retail, finance, health, leisure, media. Anything a person opens on their phone to get something done.
- 02
B2B & internal apps
Tools for organizations, field management, employee apps. Operational, stable, working.
- 03
E-commerce apps
Native stores. Fast, smooth, one-tap checkout. Higher conversion than mobile web.
- 04
SaaS apps
A mobile companion to an existing product — or a platform that's mobile-first from day one.
- 05
AI-powered apps
Smart chatbots, image and document scanning, personalized recommendations, AI agents. On mobile and on-device.
- 06
PWA
Progressive Web Apps. Sometimes a native app isn't the answer. PWAs deliver an app-like experience — no stores, no download.
// 02 · Approach
Native, Cross-Platform, or PWA — which fits you?
This is the first question we help you answer. There's no single right answer. We don't push technology — we recommend based on the project.
- 01 · Maximum performance
Native
Swift / Kotlin
+ Maximum performance, full access to device features, perfect experience.
− Two codebases, double the development, double the maintenance.
- 02 · The fast lane
Cross-Platform
React Native / Flutter
+ One codebase for both platforms: most screens and logic are written once, so there is less duplicated work in development and maintenance. Performance close to native for most business apps.
− The saving depends on the product: platform-specific capabilities, integrations, testing on both platforms and product scope still drive the effort. For extreme performance or heavy graphics — go native.
- 03 · No app stores
PWA
Progressive Web App
+ A website that behaves like an app. No download, no updates, no store.
− Great for some products — not all. Limited access to full device capabilities.
// Apps we built
Apps we built — running in production
Not a logo wall. Four products running in production, with what we built in each and why. Full case studies one click away.
React Native · Web · AI · Admin
Mystorya
An end-to-end personal-guidance app: iOS, Android and web from one codebase, an AI chat fluent in astrology, numerology, tarot and palmistry, a daily reading, a multi-layer memory system, an admin console and cloud infrastructure.
Read the Mystorya case studyiOS · Android · AI · Data
Onit
An end-to-end health-tech app: iOS and Android, an appointment matching engine, insurance policy analysis, claims and refunds, a conversational AI assistant and user-data analytics.
Read the Onit case studyiOS · Android · Realtime backend
Tory
A client app, a driver app and a real-time dispatch layer for on-demand mobile services — location-based matching, live map tracking and secure in-app payment.
Read the Tory case studyReact Native · Web · Backoffice
Dividandy
A fintech gaming platform: competitive trading tournaments with virtual capital, a simulated engine on live market data, live leaderboard, wallet and KYC.
Read the Dividandy case studyWeb · Native apps · Fintech data
Planner
A wealth-management platform consolidating investments, cash, pension and exposures — web, native apps, multi-currency, multi-portfolio, RTL/LTR and security.
Read the Planner case study
// 03 · Technology
Our stack
A full stack — from native iOS to backend to push notifications. We pick the right tool for each app, and we know each of them deeply.
- iOS
- Swift
- SwiftUI
- UIKit
- Core Data
- Android
- Kotlin
- Jetpack Compose
- Coroutines
- Room
- Cross-Platform
- React Native
- Flutter
- Expo
- Backend
- Node.js
- Python
- Firebase
- Supabase
- Real-time
- WebSockets
- GraphQL Subs
- Pusher
- Push & Analytics
- FCM
- APNs
- OneSignal
- Mixpanel
- Amplitude
- AI
- OpenAI API
- Claude API
- On-Device ML
- Core ML
- DevOps
- Fastlane
- App Center
- TestFlight
- Crashlytics
// 04 · How we work
How we work
- 01STEP 1
Understand the product
Who is the user? When will they open the app — coffee in the morning, couch in the evening, on the bus? Every detail shapes the design.
- 02STEP 2
Mobile-first UX
Mobile isn't a tiny desktop. One hand, small screen, short bursts of attention. We design for the real experience.
- 03STEP 3
Platform-native design
Material Design for Android, Human Interface Guidelines for iOS. Or a custom design that works beautifully on both. No generic templates.
- 04STEP 4
Iterative development
Two-week sprints. At the end of every sprint — a live build you can install and try. You don't wait two months to see if it works.
- 05STEP 5
Testing on real devices
Not just simulators. Real iPhones and Androids, different OS versions, different resolutions. "Works on my machine" doesn't fly on mobile.
- 06STEP 6
Store launch
We handle the App Store and Google Play submissions. ASO, screenshots, descriptions, responses to rejections. You don't deal with any of it.
- 07STEP 7
Post-launch maintenance
iOS and Android updates ship constantly. We update, fix, add features. Your app never falls behind.
// What a project includes
What you get in an app development project
App quotes are hard to compare when it's unclear what they include. This is the work that makes up a project with us — and what in each row depends on your scope. The binding content of each row is fixed in the scope document agreed before work starts.
| Deliverable | What's included | What depends on scope |
|---|---|---|
| Discovery & requirements | Who the user is, when and how they open the app, what's in version one and what isn't. You leave with an agreed scope before any code is written. | Depth of discovery: an idea without a document needs more joint work than an existing requirements document. |
| Mobile UX & UI | Flows for a small screen and one hand, Material Design for Android and Human Interface Guidelines for iOS, or a custom design that works on both. | Number of screens and states (empty, loading, error) and a dedicated tablet layout. |
| The app itself | Native (Swift/Kotlin), cross-platform (React Native/Flutter) or PWA — based on a reasoned recommendation for the project, not on the technology we find convenient. | One platform or two, offline support, push notifications, camera and location features. |
| Backend, database & API | Most apps need a backend. We build the whole stack — server, database and API — or connect to an existing one. | Real-time, roles and permissions, an admin interface, data volume. |
| Integrations | Notifications (FCM/APNs), analytics, AI services via API or on-device — whatever the product actually needs. | How many external systems, whether they have an API and documentation, and who holds the credentials. |
| Testing on real devices | Real iPhones and Androids, different OS versions and resolutions. An installable build at the end of every sprint. | The device matrix and the test scenarios your audience requires. |
| Store launch | App Store and Google Play submission: ASO, screenshots, descriptions and responses to rejections. The code and store accounts are yours. | Whether developer accounts already exist, and what the organisation needs to provide for them. |
| Post-launch maintenance | iOS/Android updates, bug fixes and new features. We agree up front what maintenance covers and what is a follow-on project. | Support scope, response times and whether ongoing development is needed. |
- 01
Discovery & requirements
Who the user is, when and how they open the app, what's in version one and what isn't. You leave with an agreed scope before any code is written.
What depends on scope: Depth of discovery: an idea without a document needs more joint work than an existing requirements document.
- 02
Mobile UX & UI
Flows for a small screen and one hand, Material Design for Android and Human Interface Guidelines for iOS, or a custom design that works on both.
What depends on scope: Number of screens and states (empty, loading, error) and a dedicated tablet layout.
- 03
The app itself
Native (Swift/Kotlin), cross-platform (React Native/Flutter) or PWA — based on a reasoned recommendation for the project, not on the technology we find convenient.
What depends on scope: One platform or two, offline support, push notifications, camera and location features.
- 04
Backend, database & API
Most apps need a backend. We build the whole stack — server, database and API — or connect to an existing one.
What depends on scope: Real-time, roles and permissions, an admin interface, data volume.
- 05
Integrations
Notifications (FCM/APNs), analytics, AI services via API or on-device — whatever the product actually needs.
What depends on scope: How many external systems, whether they have an API and documentation, and who holds the credentials.
- 06
Testing on real devices
Real iPhones and Androids, different OS versions and resolutions. An installable build at the end of every sprint.
What depends on scope: The device matrix and the test scenarios your audience requires.
- 07
Store launch
App Store and Google Play submission: ASO, screenshots, descriptions and responses to rejections. The code and store accounts are yours.
What depends on scope: Whether developer accounts already exist, and what the organisation needs to provide for them.
- 08
Post-launch maintenance
iOS/Android updates, bug fixes and new features. We agree up front what maintenance covers and what is a follow-on project.
What depends on scope: Support scope, response times and whether ongoing development is needed.
Not sure yet what belongs in version one? We have a filled-in requirements document example, with a file to download. App requirements document example — downloadable template
// Before you choose a vendor
Six questions that define the scope — before the quote
App quotes look different because every vendor assumes something different. Answering these six questions makes quotes comparable — and the spec precise.
- 01
A new product or an existing one?
For an existing product the first question is who holds the code, the cloud accounts and the store accounts today — and in what state. Without that, no estimate holds.
- 02
Native, cross-platform or PWA?
The choice follows the product: hardware, offline, the team that will maintain it and budget — not the trend. A good vendor explains the recommendation rather than offering what suits them.
- 03
What is the budget, and what should it include?
A budget without a scope list is a number in the air. Ask every vendor what is included — spec, design, backend, testing, store launch and maintenance — and only then compare.
- 04
What goes into the first version, and what doesn't?
An MVP is a decision about what to leave out. A short requirements document, stating what the first version must let the user do, saves quote rounds and mid-project changes.
- 05
Who maintains it after launch?
iOS and Android updates, fixes and new features are part of the product's life. Agree up front what maintenance includes, what counts as a new project, and the response times.
- 06
Who owns the code, and what is handed over?
The code, the store accounts and the infrastructure should be in your name from day one. Check that handover includes documentation and access — not just an installable build.
// 05 · Who it's for
Who this is for
- 01
Startups
Need an app as their primary product. Fast MVP first, scale later.
- 02
SaaS companies
Need a mobile version of an existing product. An app that feels like part of the product — not an afterthought.
- 03
Businesses
Want a customer app — ordering, loyalty, notifications, retention.
- 04
Enterprises
Need an internal app for field workers and operational teams.
// 06 · Why us
Why us
- 01
Mobile is a craft
Not every web developer knows mobile. We work on mobile every day, know every pitfall — and how to step around it.
- 02
End-to-end ownership
From discovery to App Store approval. You don't manage vendors — we manage everything.
- 03
Availability, defined up front
A bug on mobile means customers walking away. Response times and the emergency path are set in the maintenance agreement — before launch, not after the incident.
- 04
Experience you can see
Not a logo wall — apps running in production today, shown above with what we built in each and why. You get the experience — without having to make the mistakes.
// 07 · FAQ
Frequently asked questions
01.How much does it cost to build an app?
It depends on complexity — and mostly on how many specialists are involved. In Israel in 2026, with a professional team: a simple MVP — ₪80K–180K (~$22K–50K); a medium app or SaaS — ₪250K–700K (~$70K–195K); an app with AI and realtime — ₪400K–1.2M (~$110K–330K). The full breakdown (backend, AI, DevOps, maintenance) is in our cost guide. A precise number comes after one discovery meeting.
Full guide: how much app development costs in Israel in 2026
02.We have an idea but no spec — what should we prepare before reaching out?
You don't need a perfect document. It's enough to define in plain language: which problem the app solves, who the users are and what each may do, the main flow from start to finish, and what is explicitly not in version one. We fill in the rest together during discovery. We've published a filled-in example of such a document, with a Word template to download.
App requirements document example — a filled-in template to download
03.How long does it take to build an app?
It depends on the agreed scope. The orders of magnitude we plan around — not a commitment: a focused MVP with one or two user roles and no complex integrations — 8 to 12 weeks; a medium app with a backend, permissions and integrations — 4 to 6 months; an enterprise project with many roles and systems — 6 to 12 months. The binding schedule is set after discovery and also depends on availability on your side and on your existing systems.
04.React Native or native — which is better?
It depends on the project. Most business apps get a great result with React Native, because screens and logic are written once for both platforms — less duplicated work, and one team maintaining one version. How much that saves depends on the product: integrations, device capabilities and testing on both platforms remain either way. For extreme performance needs, heavy graphics, or deep device feature usage — go native.
05.Do I need an app, or is a responsive site enough?
Great question — not every product needs an app. If there's no recurring use, no offline need, and no push notifications — a responsive site or PWA is enough. We'll tell you straight.
Websites & web systems — when a responsive site is the right answer
06.How do we work with you — fixed price, hourly, and who manages?
Both, depending on what fits the project: a scope defined in a document — fixed price with acceptance criteria per stage; a product that evolves as you go — hourly with a cap, or a team at a fixed monthly capacity. In every track there is a project lead on our side who is accountable to you, two-week sprints with an installable build at the end of each, and product decisions stay with you. Whatever is agreed is written into the agreement, including what post-launch maintenance covers.
Defined project or ongoing team — how to choose, and who is responsible for what
07.Who owns the app and the code?
You do. No "buts." Your code, your store accounts, everything is yours.
08.Do you handle store submissions?
Yes. App Store and Google Play — we handle everything: ASO, screenshots, descriptions, responses to rejections (there's always a first rejection).
09.What about post-launch maintenance?
Launch isn't the end — it's the beginning. iOS/Android updates, new features, bug fixes, optimization. We stay with you.
10.Do you build for tablets too?
Yes. iPad and Android tablets. A proper adapted design — not a stretched phone screen.
11.Do you build the backend too?
Both. Most apps need a backend — server, database, API. We build the whole stack.
Software & systems development — the backend, API and infrastructure behind the app
12.Do you integrate AI into apps?
Yes. Chatbots, image scanning, smart recommendations, AI agents. Both through external APIs (OpenAI, Claude) and on-device models.
Last reviewed:
Related reading
Guide
How much does app development cost in Israel in 2026?
A real cost breakdown: MVP, Backend, Realtime, AI, DevOps and maintenance. Realistic ranges, no clickbait numbers, with hidden costs people discover too late.
Guide
App requirements document example — a filled-in template to download
What to define before asking for a quote: users and permissions, flow and states, scope and exclusions, screens with failure states and acceptance criteria. Includes a Word file to work in.
Guide
React Native vs Flutter in 2026 — what's actually right for startups?
Long read: performance, hiring, OTA, scale, web synergy and time-to-market. The pragmatic call for most 2026 startups.
Comparison
React Native vs Flutter — which to pick in 2026
Cross-platform framework comparison: performance, native module access, maintenance cost, talent pool, and OS updates. Recommendation by product type.
Case study
Case study: Mystorya — an AI companion that remembers your story
An end-to-end personal-guidance app: iOS, Android and web, an AI chat fluent in astrology, numerology, tarot and palmistry, a daily reading, a multi-layer memory system and an admin console.
Case study
Case study: Onit — a doctor's appointment in days, with AI and data
An end-to-end health-tech app: iOS and Android, an appointment matching engine, insurance policy analysis, claims and refunds, a conversational AI assistant and user-data analytics.
Case study
Case study: Dividandy — a real-time competitive trading game
A fintech gaming platform: trading tournaments with virtual capital, a simulated engine on live market data, leaderboards, wallet and KYC — on iOS, Android and Web.
Case study
Case study: Tory — on-demand mobile services
We built a client app, a driver app, and a real-time dispatch backend from scratch. Architecture, matching engine, and an order flow measured in seconds.
// 08 · Let's talk
Got an app idea?
A 30-minute intro call. No strings attached. We'll figure out together if we're a fit.
Straight. To the point. On time.