-
Notifications
You must be signed in to change notification settings - Fork 219
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
Android&iOS using of this library #253
Comments
Technically yes, but it's untested for that purpose. The windowing backend supports mobile, and WebRender supports mobile, too. I'm not sure whether it works, because I haven't tried getting it to run on mobile. You might find these instructions helpful. |
@fschutt sounds great! And what about iOS? The same way? |
Yes, the same. It may work, but I can't test it. Windows - Mac - Linux Desktop and WASM are the targets right now. |
@fschutt guys, look... you definetely should try to make it run under Android and iOS. Pretty sure there are a lot of opportunities and scope of application on those markets specially for Azul. Not many really fast and lightweight App engines there on mobile. Flutter, Native, React Native (lol) and that's all. If Azul would create builds for mobiles that would be really stunning. |
I wonder if there are any CI providers of free Android & iOS plans this project could leverage to automatically build it upon each commit on these platforms. Does anyone know about such services? This wouldn't substitute testing on these platforms but would IMHO significantly lower the bar for adoption by newcomers for basically zero effort from @fschutt and co. |
@dumblob CicleCI provides testing for Android and iOS for winit AFAIK. Also, since Azul is 99% Rust (only a bit of C), it should be easy to cross-compile. However, right now I'm only working on getting it 100% running on Windows first, every other platform can come later. I simply don't have the time right now to support 5+ platforms and four compilation targets (C, C++, Python, Rust) alone. While the API itself is good (the architecture is ok, I've tested Azul in practice), it may still take a while unti a 1.0 (Windows-Mac-Linux-only) release. |
Makes sense to first target the "primary" platforms and after some minimal "MVP-like" stabilization jump on Android & iOS CI (and if there is commercial interest, build a community around full-featured Android & iOS support instead of just plain CI building). |
Can Azul be used in Android & iOS development?
The text was updated successfully, but these errors were encountered: