As a suggestion, I think you could state more strongly that this is a code editor that runs on Android, rather than a code editor for things that run on Android.
The demo photos definitely cleared it up for me, but the build instructions at the beginning for Mac/Linux/Windows seemed to contribute to the issue.
I can only relate my own experience. I got excited about coding on Android, and bought a tablet when the first version came out that supported Python. It turned out that coding on the tiny screen was a chore, even with a keyboard, programming Android was harder than I expected, and... the biggest thing was that since the start of the smart phone era, I simply haven't had a good enough idea for an app.
> the biggest thing was that since the start of the smart phone era, I simply haven't had a good enough idea for an app.
Doesn't matter if you do, some dodgy company in a foreign country will happily wrap your app in ads and somehow be higher in the search results than your app[1].
If it's a really good idea, someone like Zynga will simply write a polished clone and make millions off your idea while your original app still doesn't show up in the search results.[2] Or anywhere, for that matter.
[1] I wrote an app in 2012 or thereabouts and this happened to me. I don't know if it is still possible.
Yes, I assumed so. The alarming part is not the formatting of the numbers, but that there's 145MB of source code and almost a GB of build artefacts... for an Android text editor. That's more code than PostgreSQL.
They are not really identical and forked from the same base project, they may have similar features.
Acode is foss,built using cordova and JS tech,has its own plugin system.
Squircle is also foss and built using kotlin.
Vscode for android is just code server inside web view wrapper or browser and embedded git.
I can't speak for the other ones as they are proprietary.
Fdroid says that not all of the code is free... What are the closed portions, anyone knows?
Edit: this seems to be due to (removed for fdroid) google integration. Feels strange... Author removes a Google library for fdroid release but is still being punished be the antifeature.
It seems to not be needed or used. My take from the thread is that F-Droid complains about the library reference present in the source code at all. It does not know the library is not linked in the F-Droid build.
AFAIU if a nonfree library can’t be disabled or patched out, the app doesn’t get to be published on F-Droid at all. The antifeature description[1] just says
> In our experience, where the upstream developer includes Non-Free libraries, sooner or later they will include more Non-Free libraries, or other Anti-Features. Frequently they become impossible to maintain/update in F-Droid.
The problem with coding on the phone is the editing experience. Phone keyboards aren't made to edit code. The only thing this editor does to improve that is to show a bunch of special characters above the standard keyboard[1]. That keyboard also has its own autocomplete function, which doesn't make sense in the context of a code editor. A code editor for the phone should implement its own keyboard.
But android autocomplete doesn't make sense for coding. A code editor that implemented its own keyboard could have something like intellisense with the UI of autocomplete.
It definitely has its quirks though so a bluetooth keyboard is probably quite necessary for anything besides a few minor edits.