Android version — would you want one, and under what name?

[Pascal-SAPUI5]

I have been sending a few fixes your way lately (#98, #99, #100) and use the app
regularly. I would like to have it on Android too — but before putting time into
that I would rather ask than assume.

Would you want an Android version of PayForMe at all? And if so, what about the
name?

Apache 2.0 does not cover product names (section 6), and I would not put
"PayForMe" on a store listing without your say-so. A few ways this could go:

1. It lives under your account as the project's official Android client, and I
   contribute to it the way I do here.
2. It is my repository but carries the name with your permission, clearly marked
   as a companion rather than the original.
3. It is a separate app with its own name, crediting this project as its origin.

Any of those works for me, including "none of the above". What I want to avoid is
building something that ends up stepping on your project's identity.

No hurry — I realise this is a side project.

[InteractionEngineer]

Hi @Pascal-SAPUI5,
I'm afraid you didn't really take the time to get to know the ins and outs of the project. It seems to me that your PR's as well as this issue were created by AI and lost all human touch. That makes me skeptical about how much of the mentioned contributions you really thought about and tested yourself thoroughly.
I have nothing against the use of AI for this repo but it shall always support you (a human developer with free time on hand to invest in community projects) – not take over the work. You have to understand the code to catch errors AI will inevitably make. And from the text style of both your PR's and this issue it seems more like OpenClaw was tasked to do work at my repo, mostly unsupervised, which is not what this project is for.
Please feel free to answer if I misunderstand something. But answer yourself, please.

[InteractionEngineer]

(What made this abundantly clear to me is that there are at least two Android clients already.)

[Pascal-SAPUI5]

Fair enough, and thanks for saying it directly.

Still, I would like to point at the substance. PR #98 fixes a data loss bug that magshee ran into independently while working on #42. She is asking about the same field over there right now. PR #99 addresses the project name versus id confusion that four different people reported between 2022 and 2023, and that Hustenbonbon offered to accept a PR for back then. PR #100 fixes a silent failure that your own test file already marked with a note saying it should emit once proper feedback exists.

Every one of them ships tests for the cases people actually reported, including "Spongebob house" and "something + somethingelse". The app also runs on my own iPhone through TestFlight.

About how I work. Agentic coding is my daily practice in SAP adjacent enterprise development, and I hold it to the same standard as anything else I ship. Tests, review, understanding what changed and why. I take your point that the writing style gave it away, and that this may not be what you want in your repo. That is your call to make.

If you would rather I close the PRs, just say so.