Colada App

The challenge

Three engineers from Bilbao validated the Colada concept during the pandemic: a platform connecting users with verified Coladers to outsource washing, drying and ironing. Launching the service required two distinct native iOS apps: one for the end user requesting the service, and one for the Colader managing orders, rates, schedule and deliveries. Time-to-market was tight and technical quality was critical to support the brand from day one on the App Store.

The solution

AtalayaSoft assigned Francisco José García Navarro as the senior iOS engineer responsible for Colada's native development. Francisco led the build-from-scratch of both iOS apps in the ecosystem in Swift, to ensure performance, reliability and a consistent experience with iPhone conventions. The scope was structured as two independent iOS products sharing reusable domain logic.

1. iOS app for end users

Native iPhone app for the customer requesting the service. Key features included:

• User location and map view of available Coladers in the area.
• Filtering by rate, delivery time (24/48/72 h) and services offered (wash, ironing, door-to-door pickup).
• Order configuration, Colader selection and payment.
• Order tracking with push notifications on each status change (pickup, washing, delivery).

2. iOS app for Coladers (providers)

Native iPhone app for the self-employed provider verified by the platform. Key features included:

• Colader profile management: rates, maximum accepted weight, surcharges for ironing and door-to-door service.
• Availability and pickup schedule configuration.
• Incoming order acceptance and communication with the end user.
• Push notifications for new orders and status changes.

Featured technical decisions

Two native iOS targets on a shared domain core

The architecture was organised around a shared domain core (order models, user session, backend calls, notifications) consumed by both apps via Swift Package Manager (Apple's official dependency manager for Swift projects). This avoided duplicating logic between the user app and the Colader app, reduced maintenance cost and kept both products functionally consistent as the service evolved.

100% native code for an early-stage startup

In a market where many startups choose cross-platform frameworks to accelerate launch, Colada chose native iOS from day one. The technical rationale was clear: a marketplace app with geolocation, push notifications critical to the operational flow, and two distinct user profiles benefits from native APIs in performance, stability and access to system features without intermediate layers.