-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Android #1481
Comments
Awesome! |
(I'm just a random dude / not associated with the Wails project) We're hacking on a new project using Wails. Depending on success, we're aiming for an eventual Android release. To know that it's feasible, I've hacked together enough code so the default Wails template can run on Android. I haven't integrated it into Here's some Logcat logs:
Cheers! |
Holy moley! This is amazing! Thanks so much - we will build on this post v2 release 🙏 |
what about ios target? fyne.io can do them all, let's have the main platforms(windows,linux,macos, android,ios) all with wails if feasible. |
in that case, flutter could be the way to do? for android and ios that is |
Unfourtunately, in my experience, Dart gets complicated, and NativeScript has issues. For simplicity, there is nothing like the combination of a frontend web framework for UI, and Go for all backend work. This is why Wails is a really good winning combination. Dart is good, but it can get very complicated when trying to write stateful UIs. Bundling all this together in an APK for Android would be great. |
I like wails and will wait for its android and ios support. in the meantime it seems flutter is the one most promising that covers the smartphone apps space. |
This would be absolutely amazing to have and would make wails my one-stop-shop for application development. Trying to use Flutter right now for android and boy howdy is it annoying. Hoping this makes the cut for wails v2 at some point |
wading into ios|android will be a very different and challenging task, you will have to call java-api or swift-api in the end to get all the juicy stuff from their ecosystems, golang will have to provide some bindings there, don't know how feasible this path will be. |
https://github.com/socketsupply/socket uses some clever way(json marshalling) to work with android and ios webviews, maybe Wails can borrow some ideas there to get mobile supported. yes it will lack some native api features, but it might be good enough for 90% user cases. |
FYI looks like tauri is heavily working on android support |
notably: the main author of wails created these issues, so they may in a sense be "Planned", but I don't believe any code exists yet (other than the Android PoC [0]) nor do the issues currently live in a milestone [0]: <wailsapp/wails#1481 (comment)>
notably: the main author of wails created these issues, so they may in a sense be "Planned", but I don't believe any code exists yet (other than the Android PoC [0]) nor do the issues currently live in a milestone [0]: <wailsapp/wails#1481 (comment)>
notably: the main author of wails created these issues, so they may in a sense be "Planned", but I don't believe any code exists yet (other than the Android PoC [0]) nor do the issues currently live in a milestone [0]: <wailsapp/wails#1481 (comment)>
notably: the main author of wails created these issues, so they may in a sense be "Planned", but I don't believe any code exists yet (other than the Android PoC [0]) nor do the issues currently live in a milestone [0]: <wailsapp/wails#1481 (comment)> + Update stars & Fork
It would be better for Wails to focus on desktop development, right? It seems that there’s not much necessity to support mobile development. After all, traditional hybrid solutions for mobile are already mature, and they don’t interfere with the combined use of Go. Therefore, instead of diverting energy to venture into mobile development, it would be more beneficial to concentrate on doing a good and thorough job with desktop development. |
Regarding demand, I think the reactions speak for themselves. Having said that, desktop will always be the primary focus |
If someone is interested there is an example of Linux Mobile (not Android): https://gitlab.com/dedSyn4ps3/wails-pinephone |
Supporting mobile will add momentum to this project. It will be beneficial, even if indirectly. |
Another way for build apk use |
Given the lack of commit history on this one, I don't think it's a super viable option officially long term. |
find a gradle lib |
Looks updated but with 0 documentation, do you know how to use/implement it? |
I'm currently evaluating Wails. |
Thanks for the kind words. We'd love to support mobile. |
hey @leaanthony there is a golang web view for iOS and android here. I used it ages ago and it worked ok. https://github.com/gioui-plugins/gio-plugins/tree/add-signin/webviewer I wish wails had mobile web views... |
Thanks! Why not join us on discord and we can talk about what's needed for doing it? All we need is someone to drive it. |
For mobile support, I wonder if capacitor is an option? |
The Tauri mobile integration doesn't look super complicated, something we can work with there in terms of "borrowing"? |
Hey friendly reminder, i'd be glad if it supports android |
Anyone with the skills or experience is welcome to contribute, the current limited time of maintainers is currently focused on other areas like getting v3 out the door. |
sorry @leaanthony I missed this. Happy to meet with you via google meet, signal, etc Booking Cal: Signal: https://signal.me/#eu/vgBESlcvaESbERk8FZvKoT8gTOxWwvoG2GbNlR789l4OYUmnMTtO1aiXhPiPK49t |
@gedw99 Community discussions are occurring on discord, so instead of trying to get a limited 1:1, it would be more convenient for everyone to keep the discussion public and localised to 1 platform. |
from https://wails.io/docs/community/links https://discord.com/invite/JDdSxwjhGf is dead for me at least.. Im on browser. |
@gedw99 That invite link worked for me, I created one if it is still dead https://discord.gg/MGUSPY5c |
thanks. Hmmm its will not connect to the browser version. I will not install their app. funny because the links used to work into their web browser. seriously... nuts. can we use GitHub Discussions ? |
DMed you in Discord 👍 |
We'd like to support Android as a build target
The text was updated successfully, but these errors were encountered: