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 ?
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 ?
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.
We are always happy to help!
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.
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) 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:
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!
Hey @Corner - I hope this helps, Iāve made a little video on this https://youtu.be/gXYpFN87WuU?si=iYZjoRzrDZ_-mv3g
thanks for info dude, I will try you product soon
Great - please let me know if you need any help or have any questions
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 ā¦)
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:
- Performance on mobile
- 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
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
@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.
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
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.
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
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 (free)
(didnāt try depia , itās not a comparaison just native solution alternative (I omitted solution similar depia like )
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
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 ?
it can feel like a hidden secret sauce taste , i have to admit to have no real transparency nor docs for despia
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,
and i would read this too ! Terms of Service
just sharing my honest pov !
Despia is a framework to build hybrid mobile apps using web technology - similar to capacitor, but better and way easier to use.