# Mobileraker: putting Klipper controls in your pocket > Mobileraker is a Flutter app that acts as a mobile front end for a Klipper 3D printer through an existing Moonraker installation. It covers print control, temperature, axis and fan control, a GCode console, a multi camera viewer and remote push notifications, and it can manage several machines at once. **Clon1998/mobileraker** — A Flutter mobile app for Klipper/Moonraker - Repository: https://github.com/Clon1998/mobileraker - Stars: 657 · Forks: 72 - Language: Dart - License: NOASSERTION - Published: 2026-10-21 · Updated: 2026-10-21 · Language: en - Canonical page: https://hysenlabs.com/projects/clon1998-mobileraker ## What Mobileraker actually is Mobileraker is described as a simple UI for Klipper on the phone, and the repository description calls it a Flutter mobile app for Klipper and Moonraker. The arrangement matters: you do not replace Moonraker, you connect to an existing Moonraker installation and control the printer through it. That means the app sits next to the printer's own stack rather than replacing it, which is why it can cover both a local network and a remote setup. The primary language is Dart, the default branch is master, the last push was on 2026-10-03, and the release tags are android2.9.14 from 2026-10-03, android2.9.13 from 2026-08-18 and android2.9.10 from 2026-05-31, which tells you the versioning is per platform and that the Android build is the one that is published most often. The app is on Google Play as com.mobileraker.android and in the Apple App Store, and the GitHub releases page carries the binaries. ## What you can actually do from the phone The README lists the machine commands the user gets access to, and it is a fairly complete remote control for a printer. You can pause, resume and stop a print job, monitor print progress, control all axes of the machine, control the heaters, read current temperatures, control fans, control pins such as LEDs, send GCode macros, and emergency stop the machine. On top of that come the features that make the app usable rather than merely functional: an integrated webcam viewer with support for multiple cameras, a GCode console to interact with the machine directly, a browser for the available GCode files so you can start a new print job from one of them, and temperature presets as a comfort feature. The README also notes the app can manage multiple machines, which is the feature that turns a single printer remote into a small farm remote. ## Push notifications, and the companion that makes them work The remote notification story is the part with an extra moving piece. Mobileraker lets users enable push notifications that are delivered even when the phone is not on the same network as the printer, and the README is direct that to make this work you must install and configure the Mobileraker's Companion, a separate project under the same author. The Companion is the piece that reaches your phone from outside the local network, and the README points at its own repository for the details. There is also a caveat recorded in a note above that section, and it is a real loss of function rather than a caveat about setup. Android's progress notification, the one shown in the app's screenshots, is not supported any more because of a change in a third party library, the awesome_notifications package, and the author says he will revisit the implementation if that library supports this kind of notification again, and invites contributions in the meantime. ## The origin story, and what a solo maintainer implies The README closes the General section with words from the project owner, and they are worth reading because they set expectations about the project's shape. The author is Patrick Schmidt, and Mobileraker started as a small side project with the intention of controlling a 3D printer by phone. After he posted some screenshots to the 3D printing community, public interest grew and he published it to the app stores. The key sentence for anyone evaluating the project is that he can only work on Mobileraker in his free time, and that he is thankful for support and feedback, whether through messages, store reviews or donations. That is not a complaint but it is a fact about the maintenance model, and it is the same fact the licence and repository layout point to: one person, a Flutter codebase, two app stores to release through, and a companion project to keep in step. ## Translations, and the contribution setup Localisation is handled through Crowdin, with a badge pointing at the mobileraker-app project and a crowdin.yml file in the repository root. The README says the app already supports multiple languages but relies on contributions to add new ones and to keep existing translations current, and it points at docs/contribute_i18n.md for the structure of translation keys and how to add a language. The environment setup section for contributors is a numbered list. You need Flutter and the FlutterFire command line tools installed, you import the project into your preferred IDE, and you clone the mobileraker_pro_pub repository into the same location as the mobileraker repository, because the folder structure has to look a certain way, which is the fragment shown earlier. The repository layout backs this up, with lib/ for the Dart code, android/ and ios/ for the platform projects, common/ for shared code, assets/ for images and fonts including a google_fonts directory, test/ and docs/ directories, and analysis_options.yaml for the Dart analyzer configuration. ## The limits, and what to compare it against Three things are worth weighing. The first is the lost Android feature, since a progress notification on the lock screen is exactly the thing a phone app for a slow printer exists to provide, and the README is honest that it is gone for now. The second is the dependency on the Companion for remote notifications, which means the remote use case is a two piece deployment rather than a single app, and a reader should decide whether that is acceptable before committing to the workflow. The third is the single maintainer constraint, which is a real consideration for a tool that has to keep up with Moonraker and Klipper changes on both Android and iOS. A browser-based interface you may already run is another option to weigh, though it lacks the app store distribution. Mobileraker's counterargument is the one it makes in its own words: it is a mobile app with comfort features like presets and push notifications, and it manages multiple machines. ## Conclusion Adopt Mobileraker if you run Klipper with Moonraker and want to start, stop and monitor prints from your phone, especially if you want push notifications that reach you when the phone is not on the same network. Do not adopt it if you need Android progress notifications, because the README says that feature is no longer supported following a change in a third party library. Before you rely on the remote notifications, install and configure the Mobileraker's Companion, since that is the component that delivers them, and check the licence file yourself because the repository is classified as carrying a custom licence. ## FAQ ### What is Mobileraker and what does it connect to? It is a free Flutter mobile app that works as a simple UI for Klipper on the phone. You connect it to an existing Moonraker installation and control the printer, and the app is on Google Play as com.mobileraker.android and in the Apple App Store. ### Which machine controls does Mobileraker expose? The README lists pause, resume and stop of a print job, print progress monitoring, control of all machine axes, control of the heaters, current temperature readings, control of fans, control of pins like LEDs, sending GCode macros, and an emergency stop of the machine. It also adds a multi camera viewer, a GCode console and a browser for the available GCode files. ### How do Mobileraker push notifications reach a phone that is off the local network? You have to install and configure the Mobileraker's Companion, a separate project by the same author, and the README points at that project's GitHub page for the details. The app can also manage multiple machines and offers temperature presets as comfort features. ### Does Mobileraker still show Android progress notifications? No. The README states that Android's progress notification is not supported any more because of a change in a third party library, the awesome_notifications package, and that the implementation will be revisited if that library offers support for this kind of notification again. ### What do I need to build Mobileraker from source? The README asks contributors to install Flutter and the FlutterFire command line tools, import the project into their preferred IDE, and clone the mobileraker_pro_pub repository into the same location as the mobileraker repository so the folder structure matches what the project expects. ## Sources - [Clon1998/mobileraker on GitHub](https://github.com/Clon1998/mobileraker) - [Issues](https://github.com/Clon1998/mobileraker/issues) - [README](https://github.com/Clon1998/mobileraker/blob/master/README.md) - [Releases](https://github.com/Clon1998/mobileraker/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/clon1998-mobileraker