iOS
Apps for iPhone and iPad
An experience designed for Apple devices, with navigation, visual design and device capabilities matched to the product. Includes preparation for testing and the App Store submission process.
New at AB Sites
App development · iOS / Android / PWA
Your idea.
Their next app.
From the first tap to an everyday habit. Apps that look considered, feel natural and solve a real problem for your business.
Scroll. Watch your idea take shape.
iOS + AndroidPWA · Web to app
REAL PRODUCTS. REAL SCREENS.
More than another icon.
A better wayto work. To order.To plan. To move.
We start with the people using your app: what they need to do, what slows them down today and how a complex process becomes a simple action.
01 / A business app, built for the field
BenYacovOrders
From the field.
Straight to an order.
BenYacovOrders turns a product catalogue and ordering workflow into a clear mobile experience. Choose products, specify a project and delivery address, then move through a structured order flow.
- A mobile product catalogue
- A step-by-step ordering journey
- Designed for business teams and customers
Screenshots from the BenYacovOrders app.
From browsing to ordering. Scroll to turn the screen.
02 / A progressive web app example
Vowfolio
All your plans.
One clear picture.
Vowfolio brings wedding planning into one place: tasks, guests, budgets and seating. A web product designed to follow users between desktop and mobile, with an experience suited to PWA installation.
- Tasks and a planning timeline
- Guests and budget management
- A responsive desktop and mobile interface
Vowfolio product screenshots with fictional demo data.
The right technology starts with the need.
Different ideas.
Different kinds of apps.
We choose a platform around your audience, budget and workflows. Sometimes you need an app in the stores. Sometimes a web product that opens with a link is the better fit.
Android
Apps for Android
Interfaces adapted to different devices and screen sizes, usability testing and preparation for Google Play submission. The development approach follows the capabilities your product needs.
PWA
An app that starts with a link
A responsive web product that can be added to the home screen on supporting devices and browsers. A practical direction for dashboards, customer portals, ordering and business tools.
Installation, notifications, hardware access and offline features depend on the device, browser and product design. We define and verify the required capabilities during planning.
What should you build?
| Your need | A direction to explore |
|---|---|
| A workflow customers or teams can open with a link | PWA or web application |
| A mobile experience distributed through app stores | iOS and Android |
| Advanced access to device capabilities | Platform-specific development |
| Testing an idea before expanding it | A focused first release (MVP) |
From idea to launch
A clear process.
A next step you can see.
Define the product
Identify the audience, the problem, what the first release must include and what success should look like.
Design the experience
Map screens and user journeys, build a visual language and make the important actions clear.
Build and test
Develop the agreed interfaces and integrations. Test permissions, error states, devices and screen sizes.
Launch and improve
Prepare the operating environment, support launch or store submission and plan maintenance and future releases.
DESIGNED TO WORK.
What you don’t see
needs to work, too.
An app is more than a collection of screens. We define the foundations that make it a dependable tool.
- Sign-in and role-based access when needed
- Connections to existing systems, data and services
- Admin interfaces and team workflows
- Hebrew, English and RTL / LTR layouts
- Usability, accessibility and performance checks
- Handover, maintenance and release planning
Development scope, integrations, infrastructure costs, store accounts and maintenance are agreed in the proposal after planning.
Before we begin
Good questions.
Clear answers.
How much does it cost to build an app?
Cost depends on screens, user journeys, platforms, permissions, integrations and the complexity of administration. After an initial conversation and discovery, you receive a proposal defining the scope, milestones and costs.
How long does app development take?
There is no single timeline for every product. An app with one workflow and a simple admin interface differs from a system with multiple user roles and integrations. We define the schedule after discovery and can start with a focused MVP.
What is the difference between a PWA and a store app?
A PWA is a web app that opens with a link and can support home-screen installation. A store app is distributed through the App Store or Google Play. Distribution, device capabilities, updates and running costs differ, so we choose based on the actual use case.
Does a PWA work on iPhone and Android?
A PWA is designed to work in desktop and mobile browsers. Installation, notifications and offline capabilities vary between operating systems and browsers. We test relevant devices and plan alternatives for unsupported features.
Can you develop for both iOS and Android?
Yes. The service covers planning and development for both platforms. During discovery we choose between a shared foundation and platform-specific development based on user experience, performance and required device capabilities.
Can an app connect to an existing website or business system?
Yes, where an appropriate integration is available. We review APIs, permissions, data structures and service limitations before committing to the integration. A new admin interface or data service can also be included in the scope.
Who handles App Store and Google Play submission?
Preparation and submission support can be included: test builds, screenshots, product details and store settings. Appropriate developer accounts are required, and final approval remains subject to Apple’s and Google’s review and policies.
Can the app work without an internet connection?
Some products can support local storage and partial offline workflows. Not every action can work offline, particularly when current server data is needed. We define what is stored locally, how syncing works and how errors are handled.
Do you include design, accessibility and Hebrew support?
Yes. Planning includes interface and user experience design, device adaptation and language direction, including RTL where needed. We check navigation, readability, contrast and different states. Accessibility targets and exact scope are agreed in advance.
What happens after launch?
A maintenance plan can cover bug fixes, compatibility updates, performance improvements and new features. Hosting, third-party services, backups and operational responsibilities should also be planned around the product.
The next screen could be yours.
An idea in mind?
Let’s give it shape.
Tell me what your business does, who will use the app and which action you want to make easier. That is where we begin.
Asaf Ben Yaakov / AB Sites