Not clear yet whether the scoring adapts for intentional rule-breaking, like centered or minimalist framing, or if it always pulls toward classic thirds. Would also like to see it handle portraits and landscapes differently, since ideal composition isn't one-size-fits-all.
AureaCam
Dial
nice idea, rule of thirds is one of those things that's easy to explain but hard to actually feel while framing a shot. since it needs camera access in the browser, is the scoring happening on-device or does it send frames to a server? would want to know before pointing it at anything private
AureaCam
@galdayan Hi! Great question – and I completely understand the concern.
To be upfront: all image processing runs 100% on-device. The camera feed never leaves your browser. All the scoring – rule of thirds, golden ratio, symmetry, and lighting – is calculated locally in JavaScript using your device's camera stream. No frames are sent to any server.
Now, about the login: the email and password are only used to verify if the user has purchased the full version. It's a simple license check to prevent piracy and ensure that only paying users access the complete features. No personal data is collected, stored, or shared – and you can use the demo freely without any login at all.
So: demo = no login needed. Full version = quick license verification, and that's it.
The app is designed with privacy and simplicity in mind – no tracking, no data collection, just a tool to help you learn photography.
Feel free to test the demo with confidence – your privacy is respected. 😊
Let me know if you have any other questions!
Best,
Franco
Dial
@aureacam that's exactly what I was hoping to hear, on-device only makes this way easier to recommend. one follow up - is the license check a one time thing per install, or does it ping on every launch? asking because that's usually where a "no server calls" claim quietly breaks down
AureaCam
@galdayan My honest answer to your question:
Right now, it does ping on every launch – but only for a quick license check, not for any camera data. And I'm already working on a fully offline alternative that will remove even that single call.
So: on-device processing is already 100% real. The full offline license check will make it even better.
I hope that answers your concern – and I genuinely appreciate you asking. This kind of feedback helps me build a better, more private product.
Let me know if you have any other technical questions – happy to dig deeper.
Best,
Franco
AureaCam
@galdayan The improvement I'm working on (for the next update):
I'm moving to a token-based offline verification system:
When a user purchases the app, a cryptographically signed license token is generated.
That token is stored locally on the device (in the browser's local storage).
On each launch, the app checks the token locally – no server call needed.
The token validates the purchase and the expiration (if any) without ever contacting the server.
This way:
No server calls at all after the initial token generation.
No email/password stored or transmitted.
Completely offline license verification.