Initial Android Support

Question

Initial Android Support

ogoffart opened this issue 4 years ago · comments

Olivier Goffart commented 4 years ago

This project is funded through NGIO Core via NLNet - https://nlnet.nl/project/SlintAndroid/

Here's a possible breakdown of tasks that we devised. We estimate this in the range of ~4 months of work.

Base Android Port Milestone. This milestone covers the foundation of the port, to allow for the cross-compilation of a Rust based Slint application, deployment to a device, and showing primitive graphics on the screen, including text labels. Rendering is to be done with Skia, for GPU acceleration and native looking text rendering.

Create or modify an existing example to cross-compile and deploy to the device, re-using existing crates and functionality in the Rust ecosystem.
Set up the CI system to test the build (and optionally deployment to the emulator).
#3430
Document how users can write applications for Android using Slint (https://slint.dev/snapshots/master/docs/rust/i_slint_backend_android_activity/)

Text Input Integration Milestone. This milestone covers the work to allow the user to interact with text input fields in Slint in a way that is consistent with other Android applications.

Show or hide the Android system virtual keyboard depending on focus on text input fields.
Ensure visibility of text input fields when focused and the virtual keyboard occupies a part of the screen. This includes scrolling and resizing the user interface.
Add support for text selection handles by rendering them at the correct location and allowing the user to interact with them way.

Dialog and Menu Widgets. This milestone will add first-class support for Material Design Dialog and Menu components. Dialogs in general and Menus specifically are crucial for many application workflows on Android.

Add support for dialog components in the material design style and rendering them in a way that makes them appear like native dialogs.
Add support for declaring menu structures in the Slint language, rendering them with the material design style, and obtaining the user-selected menu item choice in native code.

Date and Time Picker Widgets. This milestone will add support for Date and Time picker widgets, for use in dialogs. Both user interface elements represent complex controls and data models, due to different time zones and localization.

Add support for a widget in the material design style to allow the user to select a date, based on the system calendar and an optional provided input date.
Add support for a widget in the material design style for picking a time, based on the system time and an optional provided input time.

Update: Check the documentation to try the android backend: https://docs.rs/slint/latest/slint/android/index.html

王宇逸 · Answer 1 · Sat May 20 2023 17:37:07 GMT+0800 (China Standard Time)

Is there any progress here? I've found that both winit and glutin has Android support.

Olivier Goffart · Answer 2 · Sat May 20 2023 17:46:56 GMT+0800 (China Standard Time)

Not really. There is some work in progress to make it compile in the olivier/wip/android branch, but it doesn't work yet. Some more work will be needed to adjust the way the window is initialized.

Skilfingr · Answer 3 · Thu Jun 01 2023 23:47:50 GMT+0800 (China Standard Time)

Hi, I've forked @ogoffart 's repo and I've finally managed to build a working printerdemo example here by using cargo-apk.

The main issues I've had to solve are:

delaying the initialisation of the window, until the event loop receives a InitWindow event (which means that Android is ready to create it):
The fastest (and obviously not the most elegant) way is to block android_init using a loop. (the path I've taken)
The best way would probably be to make surface, gl context and other stuff optional, as other projects have already done.
disable fontconfig, as the ndk doesn't ship a bundled version and Android seems to ignore every self-compiled library one adds to the apk:
If I've understood correctly the code I've read, the same thing is done for wasm32 builds.

Overall, everything seems to work decently (considering that this was a test), apart from the fact that, as soon as one tries to switch app, Android destroys context and surface and the application crashes (for the same reason of point 1.).

I hope this will help to speed up the development. Thank you for your work!

Simon Hausmann · Answer 4 · Fri Jun 02 2023 01:02:27 GMT+0800 (China Standard Time)

Great work!

Simon Hausmann · Answer 5 · Wed Aug 23 2023 22:51:00 GMT+0800 (China Standard Time)

One aspect that might need support in the run-time library APIs or perhaps even the .slint language is first-class support for the Android Activity Lifecycle. The Android Activity Crate supports these state events, and we may want to integrate this with callbacks to the application - ideally in a platform independent way that the same API could be used also on iOS.

Simon Hausmann · Answer 6 · Tue Sep 05 2023 15:38:15 GMT+0800 (China Standard Time)

We've made an initial plan for how we'd like to break down the Android port and I'd like to share it here for further editing/discussion. I'll edit the current empty description of this issue for that purpose.

calvin2021y · Answer 7 · Sat Oct 14 2023 13:26:35 GMT+0800 (China Standard Time)

Is there a roadmap or plan with timetable for mobile support?

Simon Hausmann · Answer 8 · Mon Oct 16 2023 17:14:51 GMT+0800 (China Standard Time)

Is there a roadmap or plan with timetable for mobile support?

We have not made a plan beyond the breakdown and time estimate outlined in the description of this issue. We want to learn from the Android port first and then have a better idea about what additional functionality and features we need to support also iOS and mobile specific features in general. This initial work on Android is also limited to Rust as target programming language.