all - new external sample submission

[erdo]

Hello,

I've written an implementation with an architecture that is significantly different to the ones used in this repo. It uses the todo-mvp branch as a base, but there are enough changes to make the two branches not directly comparable. Some of the UI tests run without alteration, others had to be tweaked and some of them completely re-written for example.

I think it's positives are clarity and sparseness of code (even though this particular implementation is coded in Java). I've written the changes up in a blog post and the repo is here.

If you're in agreement I'd like to submit it for consideration in the list of external samples

[VaradGupta23]

Issue Summary: External Sample Submission – #633 Author: @erdo

Branch Base: Based on todo-mvp, but heavily modified.

Proposal: Submit a new architecture sample that is structurally different from the official samples.

Key Points:

Uses Java (not Kotlin).

Prioritizes clarity and minimalism in architecture.

Some UI tests reused, others modified or rewritten.

Full details shared in a blog post and GitHub repo.

Author seeks to add it to the external samples list.

Suggested Action For maintainers:

Review the external repository and linked blog post.

Verify:

Code quality and readability

Architectural novelty and value

Test coverage

If suitable, include the repo link in the README or external-samples.md file of the official repo.

[erdo]

hi @VaradGupta23 I appreciated the bump. I don't think there is much utility of going through it at this point though.

What I submitted is basically an implementation of the observer pattern which synchronizes a thin UI layer (the observer) based on state held in domain style classes which know nothing about the UI (the observables).

So it's effectively a simplified version of how a lot of Compose apps are structured nowadays (but it's pre kotlin, pre code modules, and it skips the ViewModel part)

[VaradGupta23]

Thanks for the clarification, @erdo — that context helps a lot. Even though it's older and pre-Compose, your approach still offers valuable architectural insights, especially for those exploring clean separation between UI and logic in Java. I’ll keep a reference to it for anyone interested in minimalist patterns or observer-based designs. Appreciate you sharing it!