makspll / makspll/bevy_mod_scripting
# Feature Request: Mobile Support (Android/iOS)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 649
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
Summary
It would be extremely valuable if bevy_mod_scripting supported mobile targets, especially Android and iOS.
Motivation
One of Bevy's strengths is its cross-platform nature, allowing developers to target desktop, web, and mobile platforms from the same codebase. However, the lack of mobile support in bevy_mod_scripting limits its adoption in projects that aim to release on Android and iOS.
Many developers use scripting systems for:
- Modding support
- Runtime gameplay logic
- Rapid iteration during development
- User-generated content
- Live updates without recompiling the entire game
These use cases are equally important on mobile platforms.
Use Case
I am currently developing a Bevy-based game that uses scripting for gameplay logic. While everything works well on desktop, the inability to deploy the scripting layer to Android/iOS prevents me from using the same architecture across all supported platforms.
Having mobile support would allow:
- Shared scripting code across desktop and mobile builds
- Faster iteration during development
- More flexibility for live content updates
- Broader adoption of
bevy_mod_scriptingin commercial projects
Possible Considerations
I understand mobile platforms introduce additional challenges, such as:
- Dynamic library restrictions
- JIT limitations on iOS
- Asset loading differences
- Platform-specific runtime constraints
Even partial support or documentation describing the current blockers would be extremely helpful.
Additional Context
Bevy's mobile ecosystem has been improving significantly, and mobile support would make bevy_mod_scripting an even more compelling solution for cross-platform game development.
Thanks for all the work on this project!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the existing platform and build support, then investigate the Android and iOS constraints listed in the issue. Done would require a defined and tested level of mobile support, or documentation of the blockers and supported partial scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, ios, rust
- Domain
- game-dev, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100