# Native mobile vs. web development

A native mobile app and a web app are not fundamentally different. They both offer the user a visual interface built on top of a foundation of workflows and a database. The primary difference lies in how they are delivered to the user.

A web app runs within a browser, relying on HTML, CSS, and JavaScript, and is accessed via a URL. A native mobile app, on the other hand, runs directly on a mobile device's operating system, allowing for deeper integration with device-specific features such as cameras, push notifications, and biometric authentication.

If you come from a non-technical background, and especially if you have no experience developing apps for Android and iOS, the difference between a web app and a native mobile app might not be entirely clear.

Before diving into how to build native mobile apps, let’s first explore the key differences between these two types.

### Web applications

As we've explored, a web app is a set of code files made up of HTML, JavaScript, and CSS, which all modern web browsers can interpret, display, and interact with.  In short, this means a web app operates within a web browser and cannot run independently of it.

There are many advantages to this approach. Although web browsers are developed by different companies and can have slight variations in behavior, they are all designed to maintain full compatibility with a standard set of programming languages like HTML, CSS, and JavaScript. This ensures that web apps created on platforms like Bubble can run consistently across a wide range of devices and operating systems, whether on a desktop, tablet, or smartphone.

Additionally, because web browsers are universally available and regularly updated to meet evolving standards, you don’t need to worry about platform-specific requirements. Your app can be accessed by anyone with a browser, without the need for users to download or install anything. This makes it easier to reach a broader audience while maintaining consistent functionality across various environments.

This approach also simplifies deployment and updates since changes to your app are immediately available to all users without requiring them to manually update anything on their end.

Bubble includes an advanced responsive editor that lets you design pages that automatically adjust to different devices and screen sizes. This ensures that your app’s pages look great and function smoothly whether viewed on a large desktop monitor or a small mobile screen. By adapting layouts and element sizes based on the user’s device, you can deliver a consistent, optimized experience across all platforms.

This approach makes a responsively designed Bubble app just as available on a mobile device as on a desktop computer, but from the perspective of a mobile device user, it comes with a few limitations that a native mobile app does not.

### Web wrappers and PWAs

There are various third-party and custom code solutions that allow you to publish a Bubble app to one or both app stores. Many of these options, including plugins and services, enable access to on-device features like biometrics[^1], file storage, the camera[^2], and contacts[^3]. These solutions work by “wrapping” your web app in a native container, making it distributable through app stores while still relying on web technologies. Essentially, web wrappers function like a “full-screen browser,” masking the fact that the app is running on web technology in the background.

Progressive Web Apps (PWAs) are another alternative that lets users add your app to their home screen, but PWAs have more limited access to native device features compared to fully native apps.

Both of these solutions have been around for years and currently power many successful Bubble apps in the app stores. However, they come with certain limitations. While they can offer access to native features and provide a way to distribute your app on iOS and Android, they may not fully match the performance, seamless user experience, or deeper device integration that a fully native app can provide. They also rely on third-party solutions (services and/or plugins) and/or custom code to work.

### Native mobile applications

Unlike web applications that run inside a browser, native mobile applications are specifically designed to run directly on a mobile device’s operating system, such as Android or iOS. This allows them to fully integrate with the device’s hardware and software features, such as GPS, camera, and push notifications.

Native apps offer a few key advantages. They can be installed directly from the Apple App Store or Android Play Store without relying on a third-party service, and they don’t rely on a web browser to function. They can leverage platform-specific features and design standards, giving users an experience that feels more integrated with their device. For example, native mobile apps can take full advantage of gestures, system-level navigation, and native UI components that users are already familiar with.

The two methods of development are by no means mutually exclusive; in fact, many of today’s most popular web applications offer both a web version that users can access through any browser on any device, and a native mobile app specifically built to be downloaded in one or both app stores and leverage the features of a mobile device.

#### Cross-platform compatibility

Building and maintaining native apps traditionally requires building separate versions for each platform (iOS and Android), which can be time-consuming and costly. Bubble’s Native Mobile App Editor aims to bridge that gap, allowing you to build native apps using Bubble’s visual tools, while maintaining the ability to deploy your app to both major platforms.

## FAQ: Native mobile vs web development

<details>

<summary>Why isn't the repeating group available in native mobile apps?</summary>

The repeating group is a web-specific element. Native mobile apps handle lists differently — each operating system has its own native list components, which Bubble uses instead. This maximizes both compatibility and performance, as list rendering is handled natively by the OS.

</details>

<details>

<summary>Why does my app need to ask permission to send push notifications and access device features?</summary>

Operating systems require apps to request explicit user consent before accessing device features like the camera, location, or push notifications. This is enforced at the OS level — it's not a Bubble limitation. Users can grant or revoke these permissions at any time through their device settings.

</details>

<details>

<summary>Why do I need to submit my app to the App Store or Google Play?</summary>

Apple and Google require all native apps to go through their review process before they can be distributed to users. This is a platform requirement, not a Bubble limitation. Bubble simplifies this process by handling the build and packaging for you.

</details>

<details>

<summary>Can I use the same database for both my web and mobile app?</summary>

Yes. Bubble's backend is shared across your web and native mobile apps, so both use the same database, and data types. Changes made in either platform are immediately reflected in both.

</details>

<details>

<summary>Why do elements in my mobile app look different from my web app?</summary>

Native mobile apps use OS-specific UI components and layout patterns that differ from web conventions.

</details>

<details>

<summary>Can I use plugins in my native mobile app?</summary>

Plugins can be used in native mobile apps, but they aren't cross-platform compatible. Many of Bubble's own plugins work on mobile, but third-party web plugins need to be rebuilt to support it. Use the *Mobile* filter in the plugin sidebar to show only plugins that support native mobile.

</details>

<details>

<summary>Why does my app need to be rebuilt and resubmitted for some updates</summary>

Minor updates, such as text changes and UI tweaks, can be pushed via over-the-air updates without resubmission. However, changes that affect the app's native configuration, such as adding new device permissions, require a new build and app store submission.

</details>

<details>

<summary>Can I test my mobile app without submitting it to the app stores?</summary>

Yes. You can test your app on a real device using BubbleGo during development, and use TestFlight for iOS beta testing before submitting to the App Store.

</details>

<details>

<summary>Why are some web elements not available in native mobile?</summary>

Many web elements rely on browser APIs and web technologies that don't exist in a native mobile environment. Bubble provides native equivalents where possible, but not every web element has a direct mobile counterpart.

</details>

[^1]: In this context, *biometrics* refers to allowing users to log in using their device's biometric methods, such as fingerprint or face recognition.

[^2]: The *camera* in this scenario means access to the on-device camera of a phone or tablet.

[^3]: *Contacts* in this scenario means to have access to the contact list (or phone book) stored on the device.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://manual.bubble.io/help-guides/getting-started/building-for.../native-ios-and-android/native-mobile-vs.-web-development.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.