dioxus
dioxus copied to clipboard
Dioxus Desktop & Mobile Native APIs
Feature Request
To unlock the full potential of Dioxus in desktop & mobile and empower developers to build high performance desktop & mobile applications, We should be adding essential native APIs from the following list:
- [ ] Camera & Microphone
- [ ] File System
- [ ] Geolocation
- [ ] Push Notifications
- [ ] Biometric Authentication
- [ ] In-App Purchases.
- [ ] App Icon Badge.
- [ ] Battery & Power.
- [ ] Tray Icon & System Tray.
- [ ] Deep Linking & URL Schemes.
- [ ] File Open Dialogs.
- [ ] Auto-Update & Self-Patching.
- [ ] Background Processes.
- [ ] LocalStorage & Secure Storage.
- [ ] Drag & Drop.
- [ ] Device Motion & Sensors.
- [ ] Vibration.
- [ ] Clipboard.
- [ ] Titlebar & Menu & Multi-Window & Fullscreen Support.
- [ ] Paypal & Stripe.
- [ ] OAuth2.
Implement Suggestion
Leveraging Tauri's plugins Rust code if allowed for Dioxus native instead of Dioxus Webview can be a solution.
most of them can be done by calling the api's directly but i'm not quite sure for background processes.
@salimmghari how is it completed ?
@salimmghari without those dioxus cannot be called a fullstack framework. it is basically useless for almost anything mobile.
I'm sorry @alkeryn , I agree with you and also I'm not a maintainer, just an user like you. I have intended to close this issue as I was informed that the Dioxus team are planning to work on Mobile and Desktop Native APIs for the 0.8 version and are currently trying to release the 0.7 version.
Add gyroscope to the list!
PayPal & Stripe and OAuth2 don’t really fit the list. As they not native apis. The first being a third-party service and the latter being a protocol.
Add gyroscope to the list!
Seconded! I really need this!
Do you all think this might accelerate the goals here? Unless I'm misunderstanding their goal. It seems like it's to accelerate the implementation of native APIs but documentation is sparse.
https://robius.rs/
Do you all think this might accelerate the goals here? Unless I'm misunderstanding their goal. It seems like it's to accelerate the implementation of native APIs but documentation is sparse.
https://robius.rs/
Care to explain how so?
@mcmah309 My apologies I only read the hero section and then when I looked at the docs I was mistaken on what they actually did. I thought they were an abstraction over native APIs via a Rust interface.