Does anyone have any deets on the rumoured support for native mobile apps? I heard timing was end of Q1 but would love to here deets about how this will work…
@fredo22 you “heard timing was end of Q1”, what was your source? It is really coming?
Last update in July 2023 from @Quentin wasn’t as promising as the one had three months before back in May 2023. May me think WeWeb perhaps postponed it
I heard Q1 as well on an office hours, I’m anxiously waiting for this to come out!
Thanks @mark !
I actually found the Office Hours recording in Youtube (from Nov 22, 2023). Title: “WeWeb Office Hours - Roadmap for the end of 2023 and early 2024 …. ” Here direct link to the timestamp (19:56):
https://youtu.be/XShje5PRsac?list=PLvTqMLG5UNf4fw-XqL-WB5wE0emIdjsmS&t=1196
Here the text for that timestamp or segment (19:56 - 20:39), a bit more than a minute:
“…and the other focus, another part of the the team will work on mobile feature, to be specific on PWA feature we want to support anything with the PWS, so you can use notification, biometric, bluetooth … basically everything you can have and play with in PWA; and so I hope we’re going to be able also to give you a way to ship those PWA as a mobile application into stores, into iOS stores and Play Store from Google. So this is what’s in the roadmap for the big things in the roadmap…”
So… seems like the “native mobile apps” implementation are more like using PWA “wrappers” (not sure what the right term would be), it sound interesting, and they mention publishing on Apple and Google App Stores,
So having then a couple of questions:
1) MAP PERFORMANCE with PWA apps. The app I’'m working is based on a Map (and user location, locatization, access to phone gps etc). In 2024 PWA wrappers are expected to have performance issues (e.g., take time for the map to load frustrating the user, doing pinch and zoom, etc)?
2) PAYMENT FEATURE with PWA apps. If payment features (e.g, paying with Apple Pay, Google Pay) are implemented on original web app in Weweb, would that functionally expected to carry over on the PWA wrapper and continue to work seemlessly?
Would very much appreciate anyone familiar with PWA’s, or on WeWeb’s implementation plan, for sharing any thought.
Hi guys, have any of you done any work pushing / converting a WeWeb project to an app store?
@Joyce any additional details to share here? Very curious and this would help inform our product strategy for the rest of the year (PWA vs. native mobile, functionality, etc.).
Thanks for the help!
Jack
Hi @Jack
We’re planning to release a PWA plugin that will add a number of functionalities to the current PWA in the coming weeks.
This will include features like:
- a workflow action to install the app on the phone (so you’ll be able to display a button that invites the user to do that in your app)
- additional geo location features
- a workflow action to share the app
- triggering vibrations, and more
But will NOT include (for now):
- push notifications
- a feature to wrap the PWA and push it to app stores
Push notifications are still top of mind for us but we’re taking our time because we want to choose an approach that ages well
Thanks @Joyce! Do you have an idea on a more specific date by when thus will be released? Thank you!
Any news on native apps?
Hi @guisalomao
Yes, it’s not a priority for now. If you’re interested in the larger vision for WeWeb in the coming months, we did a live Q&A with Raphaël back in June that explains what we prioritized for the rest of 2024 and why:
Curious if anyone has tried using Capacitor with WeWeb via the NPM plugin… I’m not well versed in this stuff, so maybe this doesn’t make sense. But just looking at how to use Capacitor, it seems like maybe a possibility through this route. Thoughts? Attempts? Still dreaming of releasing WeWeb apps on mobile app stores.
You can create mobile apps with https://www.pwabuilder.com/ pretty easily.
Oh interesting, hadn’t come across that one. I don’t see any pricing listed… is this a free service?? Thanks for sharing, I’ll have to try that!
It’s completely free, yes!
That’s awesome! Doing my best to learn these processes… Would this require exporting code from WeWeb? Or is it more of a matter of pointing something to the site that lives in WeWeb still?
Just pointing it, no exported code.