Skip to content
Botmer International®
Portl / Passport V3

App rescue · Staff augmentation

Stabilising Portl, then staying to build what came next

Portl is a social discovery and hospitality app for finding venues and events, joining guestlists, and booking experiences. Botmer began with a three-month stabilisation and rebuild, then continued as an embedded engineering partner.

Portl and Passport V3 mobile event discovery, booking, filtering, and membership screens
Portl product interfaces spanning discovery, guestlists, venue experiences, filters, and member flows
Jan 2024Botmer engagement began
3 monthsInitial stabilisation and rebuild
OngoingEmbedded feature development
Project snapshot

The engagement at a glance

Public product facts are separated from Botmer's engagement record so the delivery scope remains clear and reviewable.

Industry
Hospitality and social discovery
Location
Dubai, United Arab Emirates
Platforms
iOS and Android
Initial engagement
App rescue and rebuild
Initial phase
Three months
Partnership today
Ongoing staff augmentation

01 / Product context

About Portl

Portl describes itself as a social lifestyle platform for discovering restaurants, beach clubs, nightlife, and events. People can browse experiences, join guestlists, book tables, and see who else is going.

The product is available for iPhone and Android under Portl, while its earlier Passport V3 identity remains part of the engagement history. Its public store listings also describe profiles, social connections, venue discovery, bookings, guestlists, and member experiences.

02 / Starting point

A product that needed to become dependable

Portl, then operating as Passport V3, approached Botmer in January 2024. According to the engagement brief, the mobile product was affected by crashes, lag, and security gaps that made dependable use and continued feature delivery difficult.

Engagement priorityStabilise the live product, rebuild the foundations that required it, and create a path for continued delivery

The work began as an app rescue with a full engineering team rather than a narrow feature assignment.

03 / Delivery scope

What Botmer did

Botmer assigned a full engineering team to the product. The initial phase combined immediate stabilisation with deeper rebuilding work, covering the areas supported by the approved engagement record.

  1. 01Stabilisation
    Addressed the crashes and reliability issues affecting the existing mobile experience.
  2. 02Performance work
    Worked on the lag and product responsiveness that shaped day-to-day use.
  3. 03Security remediation
    Closed security gaps identified as part of the incoming application state.
  4. 04Application rebuild
    Rebuilt the areas that could not be made dependable through isolated fixes alone.
  5. 05Feature development
    Continued shipping product work after the initial rescue phase.

04 / Working model

From rescue team to embedded partner

The engagement started with a dedicated team focused on stabilising and rebuilding the app within the first three months. Once that phase was complete, the relationship shifted into ongoing staff augmentation, with Botmer engineers continuing full-time feature work alongside Portl.

This continuity kept product knowledge inside the working team and avoided a disruptive handoff immediately after the rebuild.

05 / Public product

The product today

Portl's current public experience centres on social discovery for hospitality and events. The official website and store listings show venue browsing, event discovery, guestlists, table bookings, social profiles, and ways to see or connect with people attending.

Portl publishes its own adoption figures on its website. Those product-reported figures describe the current platform and are not presented here as outcomes attributable to Botmer's engineering work.

07 / Supported outcomes

What changed through the engagement

The approved engagement record supports three clear outcomes: the incoming product was stabilised, the application was rebuilt within the initial three-month phase, and the relationship continued as an ongoing engineering partnership.

  1. 01Initial rescue completed in three months
    The stabilisation and rebuild phase moved the product beyond the crashes, lag, and security gaps described at the start.
  2. 02Ongoing engineering capacity
    Botmer engineers remained embedded for full-time feature development after the initial phase.
  3. 03Live mobile availability
    Portl currently maintains public iOS and Android listings. This confirms platform availability without assigning public adoption metrics to Botmer.

08 / Capability areas

Delivery across the product lifecycle

The public case study stays at capability level because an approved framework or infrastructure inventory was not provided.

01 / MOBILE

Mobile product engineering

Stabilisation, rebuilding, and continued delivery across a consumer mobile experience.

02 / RELIABILITY

Performance and reliability

Work directed at the crashes and lag affecting dependable use.

03 / SECURITY

Security remediation

Addressing security gaps found in the incoming product state.

04 / TEAM

Embedded engineering

Full-time feature delivery through an ongoing staff augmentation model.

09 / Continued delivery

An ongoing product partnership

Portl remained with Botmer after the initial three-month phase. The current working model is ongoing staff augmentation, with embedded engineers supporting continued product development rather than a closed handoff.

10 / Public references

Sources and claim boundaries

Product descriptions and platform availability were checked against official public sources. Delivery scope and the three-month timeline come from Botmer's approved engagement brief.

Build with an embedded team

Need senior engineers embedded into your product team

Share the product, current constraints, and delivery priorities. Botmer will recommend a suitable engineering path.

Discuss your project