Placing projects in /Android/data/com.tyron.code/files is too restrictive. Please move them to public storage (e.g., /storage/emulated/0/CodeProjects) so they can be accessed easily by standard file managers.

[sc1986]

Placing projects in /Android/data/com.tyron.code/files is too restrictive. Please move them to public storage (e.g., /storage/emulated/0/CodeProjects) so they can be accessed easily by standard file managers.

[TheRandomCrafter83]

They should actually be moved to the Documents directory. Emulated/0/documents/CodeAssist

[TheRandomCrafter83]

In this case though, the files can still be stored in the apps directory, but they can be made Accessible via documents.

[tyron12233]

While moving project files directly to the root of public storage seems like it would make things simpler, keeping them inside the app-specific directory is actually critical for performance. Public storage directories are managed under FUSE (Filesystem in Userspace), a virtual filesystem layer that acts as a bridge between the operating system and the actual storage hardware. Because every single file operation has to pass through this extra system layer, it introduces a significant bottleneck for an IDE. CodeAssist constantly indexes hundreds of source code files, resolves symbols, and performs heavy I/O operations during compilation; utilizing the app-specific directory allows it to perform direct, native filesystem operations and bypass this FUSE overhead entirely, preventing significantly slower compile times on your device.

CodeAssist implements Android's DocumentProvider API, which explicitly exposes its internal project folder to the system. This means you can easily view, edit, and manage your source files directly from the sidebar of the standard Android system file manager or any app that supports the Storage Access Framework. Additionally, for moving entire projects off the device or sharing code, CodeAssist already includes built-in import and export features, allowing you to easily package your work without sacrificing the app's native compilation performance.

[TheRandomCrafter83]

That's what I had thought you were doing. I haven't looked at any of the code though.

[vayamsrijanambykrishna]

Please see issue #1299; the dexing process enters an infinite loop, even though compiling the same project took 5 minutes with an older version of Code Assist (v 0.8). I have tested this with the updated code of my app—using both Java and Kotlin—along with Material 3 and AppCompat 1.3.1.