All services

Services

Web & mobile apps

An app people actually open — from the first version to the app stores.

I build iOS, Android and web apps from one codebase, so every change ships to every platform together. Whether it's a consumer product, an internal tool for a field team or a PWA that opens in the browser, the goal is the same: fast, simple to use, and connected to the rest of your systems.

What usually hurts

  • Two apps, double the work

    Building iOS and Android separately doubles the time, the cost and the bugs — and every feature lands on one platform before the other.

  • Stuck between idea and product

    A good idea that never ships because there's no first version to show users and investors.

  • An app that isn't connected

    An app that doesn't talk to your system, site or data becomes one more place to update by hand.

What's included

  1. 01

    iOS and Android from one codebase

    React Native and Expo: one app in both stores that feels native in each.

  2. 02

    Web apps and PWAs

    When you don't need a store — an app that opens in the browser, installs to the home screen and works offline.

  3. 03

    Notifications and device features

    Push notifications, camera, location, maps and scanning.

  4. 04

    Accounts and permissions

    Sign-up, sign-in, roles and profiles, secured on the server.

  5. 05

    Backend and admin

    The API, database and admin panel behind the app.

  6. 06

    Store submission

    Accounts, screenshots, listings, and submission to the App Store and Google Play.

How it works

  1. Define the core

    What's the one thing a user must be able to do? We start there.

  2. Design and flow

    Screens and user flow, tested on a phone before building.

  3. First version

    An app covering the core flow, shared with a group of testers.

  4. Testing and launch

    Fixes from feedback, then preparing and submitting to the stores.

  5. After launch

    Updates, crash monitoring and new features based on what users actually do.

Projects

Questions about this service

More questions? Read the FAQ

  • Native app or PWA?

    If you need a store presence, advanced notifications or deep device access — an app. If you want a fast tool for staff or customers without installing — a PWA is cheaper and quicker to build.

  • How long does a first version take?

    A first version of the core flow usually takes a few weeks to a few months, depending on the number of screens and integrations.

  • Do you handle the store submission?

    Yes — from setting up the accounts and assets to submitting and responding to Apple's and Google's review notes.

  • Can we start with a website and add an app later?

    Yes, and that's often the right path. With a well-built backend, the site and the app share the same data and API.

Other services

Contact

Have a system or app in mind? Let's talk.

Tell me what your team needs and I'll tell you how I'd build it. Call, message me on WhatsApp, or send an email.

+972 50-488-8987