---
title: "Custom application engineering · Oxarus Studio"
description: "We build the web platform and mobile app you'll offer your customers, from idea to launch, then keep growing it with you."
url: https://oxarus.com/en/studio/services
key: studio-services
route: /studio/services
unit: studio
locale: en
status: live
alternates:
  tr: https://oxarus.com/tr/studio/services
  en: https://oxarus.com/en/studio/services
documents:
  json: https://oxarus.com/machine/en/studio/services.json
  jsonld: https://oxarus.com/machine/en/studio/services.jsonld
  txt: https://oxarus.com/machine/en/studio/services.txt
schema: oxarus.machine/2.0
---

# Custom application engineering · Oxarus Studio

> We build the web platform and mobile app you'll offer your customers, from idea to launch, then keep growing it with you.

Breadcrumbs: [Oxarus home](https://oxarus.com/en) › [Oxarus Studio](https://oxarus.com/en/studio) › [App Development](https://oxarus.com/en/studio/services)

## Notices

- Interface data marked as representative is illustrative; it is not a real client, result or measurement.

## Sections

- [idea to working product.](#hero)
- [product types.](#kinds)
- [from week one to launch.](#timeline)
- [it's your code.](#handover)
- [we do the same work for ourselves.](#proof)
- [let's build your product.](#cta)

<a id="hero"></a>
<!-- section:hero component:ServicesHero kind:hero sources:messages:studioServices.hero -->

## idea to working product.

_STUDIO · APPLICATION ENGINEERING_

We build the platform you'll open to your customers, together with its mobile app. First a clickable prototype, then the real product, then launch. Code and accounts are in your name from day one.

<https://oxarus.com/en/studio/services>

- [Tell us about your project](https://oxarus.com/en/studio/services#cta-heading) → `open_page(path="/studio/services", anchor="cta-heading")`
- [How we work](https://oxarus.com/en/studio/services#timeline) → `open_page(path="/studio/services", anchor="timeline")`

- Web, iOS and Android end to end
- Clickable prototype by week 3
- You own the source code

1. Prototype
2. Design
3. Live

<!-- demo:start messages:studioServices.hero.demo -->
_Representative interface data_ · Illustrative product screens.

**Today's deliveries**

- **tabTitle:** Dispatch · Routely
- **product:** Routely

Dashboard · Orders · Map · Drivers · Customers · Settings

- **date:** Tue, Sep 15
- **search:** Search orders, drivers or addresses
- **In transit:** 38
- **Delivered:** 96
- **Delay risk:** 3
- **Avg. delivery time:** 24 min

**Live map**

- Kadıköy
- Ataşehir
- Üsküdar

**Orders**
- 0
  - **no:** #8841
  - **customer:** Bluebell Pharmacy
  - **area:** Kadıköy
  - **driver:** Emre
  - **status:** In transit
- 1
  - **no:** #8840
  - **customer:** Northside Market
  - **area:** Ataşehir
  - **driver:** Selin
  - **status:** Delivered
- 2
  - **no:** #8839
  - **customer:** Hilltop Bakery
  - **area:** Üsküdar
  - **driver:** Can
  - **status:** In transit
- 3
  - **no:** #8838
  - **customer:** Dot & Line Stationery
  - **area:** Kadıköy
  - **driver:** Emre
  - **status:** Preparing
- 4
  - **no:** #8837
  - **customer:** Harbor Café
  - **area:** Üsküdar
  - **driver:** Can
  - **status:** Delivered
- 5
  - **no:** #8836
  - **customer:** Parkview Optics
  - **area:** Ataşehir
  - **driver:** Selin
  - **status:** Delay risk

- **transit:** In transit
- **delivered:** Delivered
- **preparing:** Preparing
- **risk:** Delay risk

**Fleet**

- **vehicles:** 24 vehicles
- **active:** 21 active

- **nav:** menu
- **kpis:** summary cards
- **Live map:** map + routes
- **Orders:** order list
- **top:** search and date

- **release:** Version 1.0 is live
- **releaseMeta:** App Store · Google Play · Web

- **time:** 14:26
- **hello:** Have a good shift, Emre
- **next:** Next delivery
- **customer:** Bluebell Pharmacy
- **address:** Moda Cad. No:18, Kadıköy
- **eta:** 6 min
- **stops:** 3 stops left
- **cta:** Mark delivered

- _14:41_
  - **customer:** Hilltop Bakery
  - **area:** Üsküdar
- _14:58_
  - **customer:** Harbor Café
  - **area:** Üsküdar

- **shift:** Shift · 12/15 deliveries

<!-- demo:end -->

<a id="kinds"></a>
<!-- section:kinds component:ProductKinds kind:features anchor:#kinds-heading sources:messages:studioServices.kinds -->

## product types.

_WHAT WE BUILD_

Most projects fit one of these four patterns. Knowing which one you're closest to helps us pin down scope faster in the first call.

<https://oxarus.com/en/studio/services#kinds-heading>

- **Subscription platform** · _10–14 weeks_
  If you want to offer your product to other businesses for a monthly fee.
  - **EXAMPLE:** Appointment and shift scheduling software
  **IN THE FIRST RELEASE**
  - Company accounts and user roles
  - Subscriptions and billing
  - Admin panel and reports
  **PLATFORMS**
  Web · iOS · Android
  **TYPICAL INTEGRATIONS**
  - iyzico
  - e-Invoice
  - Google sign-in
  - Slack
  - _Representative interface data_
    - role-based menu
    - subscription plan
    - revenue report
- **Marketplace** · _12–16 weeks_
  If you're connecting buyers with sellers, or service providers with customers.
  - **EXAMPLE:** An app connecting tradespeople with homeowners
  **IN THE FIRST RELEASE**
  - Two-sided sign-up and profiles
  - Search, filters and reviews
  - Payments and commission
  **PLATFORMS**
  Web · iOS · Android
  **TYPICAL INTEGRATIONS**
  - Marketplace payments
  - SMS verification
  - Maps
  - Push notifications
  - _Representative interface data_
    - seller profile
    - search and filters
    - cart and commission
- **Booking and membership** · _8–12 weeks_
  If your customers buy a spot, a time slot or a package.
  - **EXAMPLE:** A membership app for a gym chain
  **IN THE FIRST RELEASE**
  - Calendar and availability
  - Online payment and cancellation rules
  - Reminders and loyalty
  **PLATFORMS**
  Web · iOS · Android
  **TYPICAL INTEGRATIONS**
  - Virtual POS
  - Google Calendar
  - WhatsApp reminders
  - _Representative interface data_
    - availability calendar
    - payment and cancellation
    - time slot and reminder
- **Field and mobile teams** · _10–14 weeks_
  If your team works in the field and HQ needs to keep track of them.
  - **EXAMPLE:** A work order app for technical service teams
  **IN THE FIRST RELEASE**
  - Task assignment and routing
  - Photos, signatures and location
  - Offline mode
  **PLATFORMS**
  iOS · Android · Web
  **TYPICAL INTEGRATIONS**
  - Maps and routing
  - ERP sync
  - Push notifications
  - _Representative interface data_
    - live route
    - signature and photo
    - offline tasks

- **IN THE FIRST RELEASE:** Point at an item to see where it sits on the wireframe.

**TIME TO FIRST RELEASE**

- **unit:** WEEKS

_Interface labels:_ First release

<a id="timeline"></a>
<!-- section:timeline component:BuildTimeline kind:steps anchor:#timeline-heading sources:messages:studioServices.timeline -->

## from week one to launch.

_PROCESS_

A typical first release takes twelve weeks. Every phase ends with something you can see and try.

<https://oxarus.com/en/studio/services#timeline-heading>

1. **Discovery**
   Scope, user flows and a clear first-release list.
   - Interviews
   - User flows
   - Release list
   **TEAM**
   - Product
   - Design
2. **Clickable prototype**
   A prototype you can click through on a phone or in a browser. You can show it to your customers.
   - Wireframes
   - Clickable prototype
   - User testing
   **TEAM**
   - Design
   - Product
3. **Interface design**
   Every screen designed for your brand, plus a component library.
   - Screen designs
   - Component library
   - Brand alignment
   **TEAM**
   - Design
4. **Development**
   Two-week increments, each ending with new features in the preview environment.
   - API and database
   - Web and mobile screens
   - Preview environment
   **TEAM**
   - Web
   - Mobile
   - Backend
5. **Testing and stores**
   Testing on real devices, plus App Store and Google Play submissions.
   - Device testing
   - Store submission
   **TEAM**
   - QA
   - Mobile
6. **Launch**
   The product is in your users' hands. Monthly development continues from there.
   - Go-live
   - Monitoring
   **TEAM**
   - Product
   - Mobile
   - Backend

- **done:** done
- **active:** in progress
- **next:** up next

1. **Scope sign-off**
2. **Prototype demo**
3. **Beta**
4. **Launch**

- **play:** Play
- **pause:** Pause
- **replay:** Replay
- **jump:** Go to phase
- **next milestone:** Next

_Interface labels:_ Week · What this phase delivers · PROGRESS

<a id="handover"></a>
<!-- section:handover component:Handover kind:content anchor:#handover-heading sources:messages:studioServices.handover -->

## it's your code.

_HANDOVER_

You don't end up dependent on us. When the project wraps, you have everything you need to carry on with another team.

<https://oxarus.com/en/studio/services#handover-heading>

- **All of the source code**
  In a repository under your account, with its full history.
- **Server and store accounts**
  Cloud, App Store and Google Play accounts are opened in your company's name.
- **Design files**
  Every screen and component, fully editable.
- **Setup and operations docs**
  Clear enough for a new developer to get going in a day.

<!-- demo:start messages:studioServices.handover.repo -->
_Representative interface data_ · Representative repository

- **repo:** routely

<!-- demo:end -->

<!-- demo:start messages:studioServices.handover.tree -->
_Representative interface data_ · Representative repository

- .github/
- workflows/
- apps/
- web/
- mobile/
- admin/
- packages/
- ui/
- api/
- infra/
- docs/
- setup.md
- architecture.md
- README.md

<!-- demo:end -->

<!-- demo:start messages:studioServices.handover.tabs -->
_Representative interface data_ · Representative repository

Code · History · CI/CD · Design · Docs

<!-- demo:end -->

_Interface labels:_ Click an item to see where it lives in the repo.

<a id="proof"></a>
<!-- section:proof component:OwnProduct kind:content anchor:#proof-heading sources:messages:studioServices.proof -->

## we do the same work for ourselves.

_OUR OWN PRODUCT_

<https://oxarus.com/en/studio/services#proof-heading>

Pals is the portal we build and run for educational institutions. It's used every day on web, iOS and Android. That's where we learned what it takes to ship a product and keep it running.

- Web, iOS and Android
- Flexible roles and permissions
- Active daily use

- [Explore Pals](https://oxarus.com/en/studio/pals) → `open_page(path="/studio/pals")`

> Live at EduNeta

<!-- demo:start messages:studioServices.proof.screen -->
_Representative interface data_

**Today's classes**

- **date:** Wed, Sep 16

- **Math · 9-A** · _09:00_
  - **room:** B204
- **Physics · 10-C** · _10:30_
  - **room:** Lab 2
- **Literature · 11-B** · _13:15_
  - **room:** A108

- **attendance:** Attendance taken

<!-- demo:end -->

<a id="cta"></a>
<!-- section:cta component:StudioCta kind:cta anchor:#cta sources:messages:studioServices.cta -->

## let's build your product.

_PROJECT_

Describe what you want to build in a few sentences. We'll come back with a clear first take on scope, timeline and budget.

<https://oxarus.com/en/studio/services#cta>

- [Tell us about your project](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=App%20project) → `contact(subject="App project")`

## Actions

- [Tell us about your project](https://oxarus.com/en/studio/services#cta-heading) → `open_page(path="/studio/services", anchor="cta-heading")`
- [How we work](https://oxarus.com/en/studio/services#timeline) → `open_page(path="/studio/services", anchor="timeline")`
- [Explore Pals](https://oxarus.com/en/studio/pals) → `open_page(path="/studio/pals")`
- [Tell us about your project](https://oxarus.com/en/contact?start=studio) → `start_project_brief(topic="studio")`
- [info@oxarus.com](mailto:info@oxarus.com?subject=App%20project) → `contact(subject="App project")`
- [Türkçe](https://oxarus.com/tr/studio/services) → `switch_locale(locale="tr", path="/studio/services")`

## Related pages

- [Oxarus Studio](https://oxarus.com/en/studio)