Emirates: developing a mobile MVP in our early years in Dubai<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t

\n\t\t\t\t\t

September 19, 2026<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t

\n\t\t\t\t\t

\n\t\t\t\t

\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t

Sector:<\/strong> Aviation \u00b7 Travel \u00b7 Tourism
Project type:<\/strong> Mobile App MVP
Services:<\/strong> Product discovery \u00b7 UX\/UI \u00b7 Prototyping \u00b7 Mobile development \u00b7 Product validation
Market:<\/strong> United Arab Emirates<\/p>

The context<\/h2>

Almost a decade ago, when we were beginning our international expansion in Dubai, we had the opportunity to participate in a project that perfectly represented the type of technology we wanted to build.<\/p>

A digital product for Emirates<\/strong>.<\/p>

The challenge was not to develop a gigantic application from day one.<\/p>

It consisted of something much more important:<\/p>

to turn an idea into a product that could be tested, touched, and validated.<\/strong><\/p>

That was the MVP's goal.<\/p>

---

Before building a complete product, you have to prove that it works.<\/h1>

One of the most important decisions in any technology project happens before writing thousands of lines of code.<\/p>

Is it really worth building?<\/p>

How should it work?<\/p>

What does the user need?<\/p>

Which parts are really important?<\/p>

Where is the value?<\/p>

An MVP allows you to answer those questions without assuming from the beginning the cost and risk of developing a complete platform.<\/p>

In this project we worked precisely on that phase.<\/p>

Transforming a product vision into a functional mobile experience capable of validating the proposal<\/strong>.<\/p>

---

From concept to a real mobile experience<\/h1>

The goal was to create an application that would allow users to visualize and experience how the digital relationship between an airline and its passengers could evolve.<\/p>

That meant working simultaneously on several layers.<\/p>

User experience.<\/p>

Navigation architecture.<\/p>

Interface design.<\/p>

Information hierarchy.<\/p>

Mobile flows.<\/p>

Prototyping.<\/p>

Development.<\/p>

Validation.<\/p>

Because an MVP shouldn't just be a collection of pretty screens.<\/p>

It should allow you to understand how the product would behave when a real user starts using it.<\/p>

---

Designing for a travel experience<\/h2>

Travel-related applications present a particular challenge.<\/p>

The user does not always use the application under the same circumstances.<\/p>

It may be:<\/p>

planning a trip from home,<\/p>

looking for information from the airport,<\/p>

consulting details from another country,<\/p>

preparing documentation,<\/p>

or trying to solve something quickly while on the move.<\/p>

This forces us to think about the mobile experience from a different perspective.<\/p>

The information must be clear.<\/p>

The main actions must be visible.<\/p>

Navigation should be simple.<\/p>

And technology must disappear behind the experience.<\/p>

---

An MVP to reduce risk<\/h1>

There is one idea that we continue to defend today at The Cloud Group:<\/p>

An MVP is not a bad version of a product.<\/strong><\/p>

It is a version specifically designed for learning.<\/p>

Its goal is not to contain every imaginable feature.<\/p>

Its goal is to quickly answer the most important questions about the product.<\/p>

Does the experience work?<\/p>

Does the flow make sense?<\/p>

Is it intuitive?<\/p>

Where do frictions appear?<\/p>

What should be developed next?<\/p>

And what doesn't deserve to be developed?<\/p>

Each answer obtained during this phase can save months of subsequent development.<\/p>

---

Product thinking before development<\/h1>

One of the lessons that those first international projects taught us was precisely this.<\/p>

A software company's work shouldn't begin by asking:<\/p>

What technology do we use?<\/p><\/blockquote>

I should start by asking:<\/p>

What problem are we trying to solve?<\/p><\/blockquote>

Technology comes later.<\/p>

That's why creating the MVP involved much more than programming.<\/p>

It was necessary to understand:<\/p>

• the expected experience;<\/li>
• the different user journeys;<\/li>
• priority information;<\/li>
• the main interactions;<\/li>
• the restrictions of the mobile environment;<\/li>
• and the potential evolution of the product.<\/li><\/ul>

  Only then did it make sense to turn it into software.<\/p>

  ---

  Designing for a global brand<\/h1>

  Working around an international brand also involves another level of demand.<\/p>

  A digital experience must be consistent with everything the user expects from that brand outside of the screen.<\/p>

  Design.<\/p>

  Hierarchy.<\/p>

  A feeling of quality.<\/p>

  Ease of use.<\/p>

  Consistency.<\/p>

  Every visual and functional decision contributes to that perception.<\/p>

  The challenge is not just about building something that works.<\/p>

  It consists of building something that appear to belong to the brand for which it was designed<\/strong>.<\/p>

  ---

  Our technological landing in Dubai<\/h1>

  This project also has a special meaning for us.<\/p>

  It represents an early stage in the international history of The Cloud Group.<\/p>

  When we started working in Dubai, we understood very early on that competing outside our home market required more than just development capacity.<\/p>

  We had to learn to work with:<\/p>

  global brands,<\/p>

  multicultural teams,<\/p>

  international environments,<\/p>

  projects with greater exposure,<\/p>

  and more demanding product standards.<\/p>

  That experience ended up influencing the way we approach projects today.<\/p>

  ---

  Almost a decade later, we're still starting the same way<\/h1>

  Technology has changed a lot since then.<\/p>

  Mobile applications have evolved.<\/p>

  The architectures are different.<\/p>

  Artificial intelligence has transformed what we can build.<\/p>

  User expectations are much higher.<\/p>

  But there is something that has practically not changed.<\/p>

  Before building a complex platform, we continue trying to answer the same questions:<\/p>

  What problem are we solving?<\/strong><\/p>

  For whom?<\/strong><\/p>

  What is the simplest way to prove that our hypothesis works?<\/strong><\/p>

  That's why we continue to use MVPs, prototypes, and discovery phases as fundamental tools in the development of new products.<\/p>

  ---

  What does an MVP really prove?<\/h1>

  A well-executed MVP allows an organization to:<\/p>

  Reduce initial investment.<\/strong>
  It is not necessary to develop the entire product to begin validating an idea.<\/p>

  Detect problems earlier.<\/strong>
  Changing a screen during a prototype costs much less than redoing an architecture when the product is already in production.<\/p>

  Prioritize functionalities.<\/strong>
  It allows you to separate what is important from what is merely desirable.<\/p>

  Align teams.<\/strong>
  A product that can be seen and tested generates much more concrete conversations than a hundred-page document.<\/p>

  Get to market first.<\/strong>
  Decisions are made based on evidence, not just hypotheses.<\/p>

  ---

  From Dubai to the rest of the world<\/h1>

  That MVP is part of a journey that would later lead us to develop business platforms, mobile applications, SaaS, ERP, CRM, automations and integrations for organizations in different countries.<\/p>

  But the philosophy remains very similar.<\/p>

  Don't start with the code.<\/p>

  Start with the problem.<\/p>

  Understand it.<\/p>

  Design a solution.<\/p>

  Validate it.<\/p>

  And then build.<\/p>

  ---

  A reflection almost ten years later<\/h1>

  When we look at some of our early international projects, the technology may seem outdated.<\/p>

  Devices change.<\/p>

  Frameworks change.<\/p>

  Interfaces change.<\/p>

  But good product decisions age much better.<\/p>

  Understanding the user.<\/p>

  Reduce complexity.<\/p>

  Validate before investing too much.<\/p>

  Only build what generates value.<\/p>

  That way of working still makes exactly the same sense today.<\/p>

  And it will probably still have it in another ten years.<\/p>

  ---

  Do you have a product idea but you're still not sure if it's worth building it completely?<\/h2>

  In The Cloud Group<\/strong> We help companies and innovation teams turn ideas into validatable digital products.<\/p>

  Discovery.<\/p>

  UX\/UI.<\/p>

  Prototypes.<\/p>

  MVP.<\/p>

  Mobile applications.<\/p>

  SaaS.<\/p>

  Architecture.<\/p>

  Development.<\/p>

  First we prove that the idea makes sense. Then we scale the technology.<\/strong><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

  \n\t\t\t\t

  \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"

  The Cloud Group developed a customized internal management platform for the Casa de M\u00e9xico Foundation in Spain to centralize information, digitize processes, and create a technological ecosystem prepared to evolve alongside the organization.<\/p>","protected":false},"author":1,"featured_media":32931,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"elementor_header_footer","format":"standard","meta":{"footnotes":""},"categories":[863],"tags":[800,906,905,907,904,829,828],"class_list":["post-32454","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-casos-reales","tag-apps","tag-dubai","tag-emirates","tag-prototipado","tag-tecnologia","tag-ui","tag-ux"],"yoast_head":"\n