Why I built Arclog
I was already keeping track of my anime, manga, novels and shows across four separate accounts: MAL, AniList, NovelUpdates and Anime-Planet. Switching between them every time I finished an episode or a chapter got tiring fast, and discussion was always scattered across forums and YouTube comments rather than tied to the actual thing I had just consumed.
The moment that pushed me to start building was reading Reverend Insanity from an EPUB. I wanted to talk about a specific chapter with someone who had just read the same chapter, with the right context, without spoilers leaking from later parts of the story. There was nowhere good to do that.
So Arclog became the home I wished existed. Every title gets structured per episode and per chapter threads, ratings and reviews live next to the discussion, and one account covers anime, manga, manhwa, manhua, web novels, light novels, movies, TV shows and books. I built it as my own daily driver first; everything else is a bonus.
How it was built
I'm a CSE graduate and Arclog is my first published app. Yes, it is my first, and yes, large parts of the application were written with Claude as a coding assistant. I am not going to pretend otherwise.
What I will say is this: the security primitives are not improvised. Authentication is handled by Supabase Auth, passwords are hashed with bcrypt, and all traffic uses TLS. Data lives in encrypted PostgreSQL with row level security. No admin or moderator can read your password, and that includes me. Catalog data is sourced from Jikan, AniList and TMDB, all open and credited inside the app.
Where this is going
Arclog is a long term commitment for me. I built it for myself before anyone else used it, so I plan to keep maintaining it whether the user base is ten people or ten thousand. There is no fixed roadmap, but any feature with strong user demand gets prioritised, no matter how complex.
The web app is already built and waiting in the wings. I am holding it back until the Android version has been battle tested in production and the user base is large enough to justify the wider attack surface. iOS will follow after that.
If something is missing or broken, tell me. If a feature would change how you use the app, tell me that too. This is a one person project today, but it is meant to be shaped by the people actually using it.
Get in touch
For bug reports, feature ideas, takedown notices, account recovery or anything else, the fastest way to reach me is by email.