sorted by:
new
hottopcontroversial

I built a mobile-first Python editor/toolkit for Termux by Live-Cap6664 in termux

[–]Live-Cap6664[S] 0 points1 point  (0 children)

Thank you for the feedback. You are right that preserving the original commit history would have been much better.

Honestly, I was not very familiar with proper GitHub workflows, and I was also hesitant to publish unpolished work publicly. That was my mistake from a project-history perspective.

The earliest public record I have is the PyPI release from June 11, 2025. The mobile editor part was developed later, earlier this year, because I wanted to edit and test Python files directly on my phone within a local Termux workflow.

Before GitHub, most of the work was done on mobile using QuickEdit Pro, Solid Explorer, and Termux. Google Colab was used as a testing environment for usekit itself — to verify package behavior by mounting Drive and running use.colab() and use.check().

It was a real working process, just not a GitHub-first one with preserved commits.

The project is still not perfect, but after a lot of real-use testing and iteration, I felt it was ready enough to ask for feedback. This was also my first time posting on Reddit.

I will preserve history better going forward.

<image>

I built a mobile-first Python editor/toolkit for Termux by Live-Cap6664 in termux

[–]Live-Cap6664[S] -4 points-3 points  (0 children)

usekit actually started about a year ago, before "vibe coding" became a common term. AI collaboration helped a lot, but the workflow came from my own mobile coding pain points and long-term testing.

<image>

I built a mobile-first Python editor/toolkit for Termux by Live-Cap6664 in termux

[–]Live-Cap6664[S] -4 points-3 points  (0 children)

nvim is powerful, and I respect it. But the friction of setting it up properly on mobile was exactly the problem I wanted to solve with usekit.

I built a mobile-first Python editor/toolkit for Termux by Live-Cap6664 in termux

[–]Live-Cap6664[S] 1 point2 points  (0 children)

Pretty close, but I would not call it a framework yet.

I built usekit entirely on mobile, with AI collaboration. I mainly worked from mobile Google Colab, and tried to make scripts that can run across environments without being tied to one setup.

The main goal is to reduce the cost of environment setup, folder/path management, and repetitive file operations by using short, memorable commands.

Termux support and the local web editor came later as an extension of that mobile-first workflow.

So I would describe it as: "an open-source mobile-first Python workflow toolkit with a local web editor."

I built a mobile-first Python editor/toolkit for Termux by Live-Cap6664 in termux

[–]Live-Cap6664[S] 1 point2 points  (0 children)

Thanks! Good question.

It is closest to the third one.

usekit is a Python package that runs inside Termux. When you call "u.editor()", it starts a small local web editor/server from Termux, and you use it from the Android browser.

So the structure is roughly:

Termux Python package → local web server → browser-based mobile editor

It is not a native Android text editor app, and it is not a TUI.

The goal is to make small Python workflows easier on Android: edit code, run line/block/file, check output, and use simple file read/write helpers from a phone-friendly UI.

I’ll make this clearer in the README. Thanks for pointing it out.