# Weweb X Despia : Weweb to native mobile app

**URL:** <https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245>\
**Category:** Ask us anything\
**Created:** [February 2, 2025, 5:48pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245 "2025-02-02T17:48:06Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Philibert](https://avatars.discourse-cdn.com/v4/letter/p/ee7513/32.png) [@Philibert](https://community.weweb.io/u/Philibert)\
**Post date:** [February 2, 2025, 5:48pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/1 "2025-02-02T17:48:06Z")

</div>

Hey Weweb users ! Who is using Despia to create mobile apps ? I am ! And very happy with this ! What about using this topic here to share our questions and findings ?

---

<div class="post-metadata">

**Author:** ![Corner](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@Corner](https://community.weweb.io/u/Corner)\
**Post date:** [February 11, 2025, 1:26pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/3 "2025-02-11T13:26:56Z")

</div>

Hello there ! Very good idea ! I was about to learn about Flutterflow but apparently, Despia would be a very good option.

Quick question, there isn’t a native integration between Weweb and Despia right ? I should create the bridge with the Despia API ?

---

<div class="post-metadata">

**Author:** ![despia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/despia/32/12626_2.png) [@despia](https://community.weweb.io/u/despia)\
**Post date:** [February 12, 2025, 9:08pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/4 "2025-02-12T21:08:32Z")

</div>

Hey @Corner - Despia is a highly performant alternative when paired together with WeWeb 😉

Yes - you would use our JS SDK in WeWeb Workflows to call native features and get your callback data into WeWeb.

It’s pretty simple and technically a native integration, as Despia fully supports Vue JS, there is just not a premade template in the WeWeb editor yet.

If you need any help with the integration process, please contact us at [help@despia.com](mailto:help@despia.com).

We are always happy to help! 😉

---

<div class="post-metadata">

**Author:** ![pauldev](https://avatars.discourse-cdn.com/v4/letter/p/b5ac83/32.png) [@pauldev](https://community.weweb.io/u/pauldev)\
**Post date:** [February 15, 2025, 10:53am UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/5 "2025-02-15T10:53:14Z")

</div>

Thank you for sharing the information. I was thinking about what to do if I have a project that is a native app. I’m too lazy to learn how to use a new platform. The ones I’ve used in the market, Adalo, Flutterflow, I don’t like them because their performance is very bad.

---

<div class="post-metadata">

**Author:** ![despia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/despia/32/12626_2.png) [@despia](https://community.weweb.io/u/despia)\
**Post date:** [February 15, 2025, 4:10pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/6 "2025-02-15T16:10:56Z")

</div>

WeWeb (Vue JS) is a superb tool / framework for building High Performant Web Apps, unlike Flutter 😉

- If you already have a Mobile App and are looking into building a Web App, WeWeb may be a valid option to consider.

You could maintain 2 Codebases, so having the Web App in WeWeb and the Native one in FlutterFlow, or you could use Despia ([https://despia.com](https://despia.com)) to build a Hybrid Mobile App from your WeWeb Web App including Native Features that Flutter would normally also provide such as FaceID, In App Purchases and much more.

**Helpful Videos on WeWeb Mobile Apps using Despia:**

[![](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/8/8766a814767e87076c6337dfb4be8d54e7ed4e2f.jpeg "Build Native Mobile Apps in WeWeb with Despia") ](https://www.youtube.com/watch?v=EhRSnRMPYq0)

[![](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/8/8d95d7b776848c367a56539c93cd2e8e702aae27.jpeg "Integrating Despia's SDKs with WeWeb - Build Native Apps in WeWeb!") ](https://www.youtube.com/watch?v=gXYpFN87WuU)

[![](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/3/3146ea4ba8d9d70e0935ded12953dae1a7ec7dd4.jpeg "Build iOS Hybrid Apps in WeWeb using Despia (Native Linking)") ](https://www.youtube.com/watch?v=ENEwGyJPvPo)

The benefit of this Hybrid Approach would be that you only need to maintain 1 Codebase (or better NoCode Base) - and that you have more flexibility in terms of Design and Logic than most NoCode Mobile Builders.

I hope this helps, happy building! 😉

---

<div class="post-metadata">

**Author:** ![despia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/despia/32/12626_2.png) [@despia](https://community.weweb.io/u/despia)\
**Post date:** [February 15, 2025, 4:12pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/7 "2025-02-15T16:12:40Z")

</div>

Hey @Corner - I hope this helps, I’ve made a little video on this 😉 [https://youtu.be/gXYpFN87WuU?si=iYZjoRzrDZ\_-mv3g](https://youtu.be/gXYpFN87WuU?si=iYZjoRzrDZ_-mv3g)

---

<div class="post-metadata">

**Author:** ![pauldev](https://avatars.discourse-cdn.com/v4/letter/p/b5ac83/32.png) [@pauldev](https://community.weweb.io/u/pauldev)\
**Post date:** [February 16, 2025, 7:55am UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/8 "2025-02-16T07:55:56Z")

</div>

thanks for info dude, I will try you product soon

---

<div class="post-metadata">

**Author:** ![despia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/despia/32/12626_2.png) [@despia](https://community.weweb.io/u/despia)\
**Post date:** [February 16, 2025, 7:42pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/9 "2025-02-16T19:42:05Z")

</div>

Great - please let me know if you need any help or have any questions 😉

---

<div class="post-metadata">

**Author:** ![Philibert](https://avatars.discourse-cdn.com/v4/letter/p/ee7513/32.png) [@Philibert](https://community.weweb.io/u/Philibert)\
**Post date:** [February 19, 2025, 2:56pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/10 "2025-02-19T14:56:25Z")

</div>

Also it’s a very simple workflow integrations  
For example, I made a formula “isDespiaApp()”  
Returning a boolean. If true, I use the Despia JS (like haptic feedback …)

---

<div class="post-metadata">

**Author:** ![bradley\_gibson](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/bradley_gibson/32/10492_2.png) [@bradley\_gibson](https://community.weweb.io/u/bradley_gibson)\
**Post date:** [February 20, 2025, 9:14am UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/11 "2025-02-20T09:14:18Z")

</div>

I have an upcoming client who needs a mobile app, and I need to decide soon which platform to use:

- **FlutterFlow**
- **Draftbit**
- **WeWeb + Despia**

My two main considerations are:

1. **Performance on mobile**
2. **Ease of development** (WeWeb already covers this)

Is there a way to assess performance without paying $250 just to run a test?

I’m also using @Micah’s UI kit and want to ensure all components are correctly “ported” over before making a final decision.

Weweb + Stackpack + Despia would be insane if everything works properly

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [February 20, 2025, 10:56am UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/12 "2025-02-20T10:56:05Z")

</div>

Flutterflow is the only mobile first method. The rest is just going short of performance and a lot of struggle and limitations with what you can get. Despia at the end of the day just wraps your app, so it’s more of a web view with access to many more native APIs and peripherals, rather than a fully fledged native app. If you need mobile native/first, then make yourself a favor and use Flutterflow 😄

---

<div class="post-metadata">

**Author:** ![Micah](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/micah/32/9102_2.png) [@Micah](https://community.weweb.io/u/Micah)\
**Post date:** [February 20, 2025, 3:27pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/13 "2025-02-20T15:27:11Z")

</div>

@bradley_gibson I’ve been able to purchase the iOS module of Despia.

I really haven’t seen a performance boost or degraded performance. It’s feels mostly like using a PWA.

If you just need a PWA you could probably just stick with WeWeb, but the unique functionality you get from Despia is pretty nice and easy to use.

The only thing that’s been annoying is Despia doesn’t respect env(safe-area-inset-bottom) or any env() values. So you need to make alternative solutions.

---

<div class="post-metadata">

**Author:** ![despia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/despia/32/12626_2.png) [@despia](https://community.weweb.io/u/despia)\
**Post date:** [February 20, 2025, 4:55pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/14 "2025-02-20T16:55:04Z")

</div>

I absolutely agree with @Broberto, Despia is for Hybrid Apps, it’s not made for Mobile first - If you are building something like TikTok, you probably wanna build Mobile first using something like FlutterFlow or even better “Swift UI”. But Despia could be your MPV for your TikTok app, if you already have a Web App setup. 😉 - You can always easily migrate away from Despia, when you feel like going truly native will be a better solution.

Where Despia really shines is allowing you to build a Native Mobile App with Native Features, while having a Web App (for Web Users) in one Codebase, without cutting back on the Native Stuff.

In regards of performance, there are no cutbacks with Despia, if your Web App is fast, your Mobile App will be fast.

I hope this helps you make a smart choice for your client 😉

---

<div class="post-metadata">

**Author:** ![despia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/despia/32/12626_2.png) [@despia](https://community.weweb.io/u/despia)\
**Post date:** [February 20, 2025, 4:58pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/15 "2025-02-20T16:58:48Z")

</div>

Thanks @Micah,

Yes - Despia does not support some Safari / Browser CSS methods like “env(safe-area-inset-bottom)” - due to the fact that your iOS App will run in a Swift Application and your PWA will run in Safari (Browser), but it can easily be solved be detecting if the user agent includes “despia” and then just adding a class for extra padding if that condition is met. 😉

---

<div class="post-metadata">

**Author:** ![Philibert](https://avatars.discourse-cdn.com/v4/letter/p/ee7513/32.png) [@Philibert](https://community.weweb.io/u/Philibert)\
**Post date:** [February 21, 2025, 2:02pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/16 "2025-02-21T14:02:49Z")

</div>

Yes and I would add here that what works better with weweb regarding my experience for detecting the user agent is using ‘uiid.length\>0’. This is a solution the Despia Team sent me

=\> I recommand using a global formula (isDespiaApp()), easier to update your conditions in workflows or displays 😉

---

<div class="post-metadata">

**Author:** ![Zacharyb](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/zacharyb/32/3567_2.png) [@Zacharyb](https://community.weweb.io/u/Zacharyb)\
**Post date:** [February 24, 2025, 12:31pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/17 "2025-02-24T12:31:20Z")

</div>

Play.HT (delicious DX focus on iOS solely (have their Figma plugin pretty qualitative) code export in Swift , pure native mobile app, 20$ish/month, then exporting and limit cost  
bonus point for the UX of the mobile visual dev on mobile very nicely done  
no paywall to try or any opaque barrieer

DetailPro \> Very cheap, good DX, free to try , same code export no additional cost

Origami Studio 100% free open source (from Meta) similar to Play but with a less smooth experience, still pretty complete, has its Figma plugin too, and can be macOS friendly instead of only compatible (if we take Play and DetailPro)

BuilderIO \> Generate code in SwftUI with proper frontend  
Bolt \> For Expo

just throwing few cheaper alternative with more access to how the solution is run

also of course simply : [PWABuilder](https://www.pwabuilder.com/reportcard?site=https://webboard.app) (free)  
(didn’t try depia , it’s not a comparaison just native solution alternative (I omitted solution similar depia like )

---

<div class="post-metadata">

**Author:** ![despia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/despia/32/12626_2.png) [@despia](https://community.weweb.io/u/despia)\
**Post date:** [February 24, 2025, 2:31pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/19 "2025-02-24T14:31:58Z")

</div>

Despia is a hybrid mobile app framework comparable to Capacitor (and with more native features), but way easier to setup and with automated 1 click app publishing.

PWA Builder, is just a WebView with more icon files than actual Swift files, no performance benefit or native feature at all 😉

---

<div class="post-metadata">

**Author:** ![Zacharyb](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/zacharyb/32/3567_2.png) [@Zacharyb](https://community.weweb.io/u/Zacharyb)\
**Post date:** [February 26, 2025, 8:52am UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/20 "2025-02-26T08:52:56Z")

</div>

Yeah PWA builder was just some alternative not something better or worse  
but geniounly curious compared to Tauri or mainly Electron (if we put aside Play, Builder, Bolt etc…) how despia position itself ?

---

<div class="post-metadata">

**Author:** ![Zacharyb](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/zacharyb/32/3567_2.png) [@Zacharyb](https://community.weweb.io/u/Zacharyb)\
**Post date:** [February 26, 2025, 11:17am UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/21 "2025-02-26T11:17:54Z")

</div>

it can feel like a hidden secret sauce taste , i have to admit to have no real transparency nor docs for despia 😢

> **[Why Appflow](https://ionic.io/appflow/why-appflow)**
>
> Top reasons to choose Appflow for mobile app delivery

And beside ethic consideration or else

on the legal side kind of risky to not clearly disclose it even if they has MIT liense for some aspects,

 ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/0/00de4804f324ef0e9fa38aa2c159545c711b6600.png)

and i would read this too ! [Terms of Service](https://ionic.io/tos)

just sharing my honest pov !

---

<div class="post-metadata">

**Author:** ![despia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/despia/32/12626_2.png) [@despia](https://community.weweb.io/u/despia)\
**Post date:** [February 26, 2025, 3:22pm UTC](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245/22 "2025-02-26T15:22:32Z")

</div>

Despia is a framework to build hybrid mobile apps using web technology - similar to capacitor, but better and way easier to use. 😉

[Next page](https://community.weweb.io/t/weweb-x-despia-weweb-to-native-mobile-app/16245.md?page=2)
