Android app shell plus local PDF runtime
The Android app uses a native shell to host the DayFiles PDF interface and client-side processing engines. That lets the app feel mobile-native while keeping the core supported PDF work on the device.
This approach is different from an upload-and-wait PDF SaaS app because the normal path is still local execution rather than a remote conversion queue.
Offline-ready behavior
After the app loads successfully and caches the required assets, many supported workflows can continue without a live network connection. Device storage pressure or cache clearing can remove those assets later, which may require the app to reconnect once.
Offline readiness improves convenience, but it does not guarantee every route or external support page remains available without connectivity.
File selection and export on Android
You choose the source files through Android file pickers and complete the workflow in-app. When output is ready, the app uses Android save or share flows so you can pick the destination yourself.
This keeps the final step under device control instead of automatically pushing files to a server account.