Data-heavy interfaces
Git Pretty View and Package Manager both turn raw data into something readable: charts, timelines, dependency states and filtering.
Case StudiesLive projects, the stack behind them, and a link you can open
These are real projects built and shipped by Thinakaran Manokaran, each with a live link you can open and inspect. They include MERN web applications, React sites, browser tools, a VS Code extension and published npm packages. There are no invented traffic, revenue or conversion figures - the running software is the evidence.
A portfolio screenshot proves that a page once looked a certain way. A live URL proves the thing still works: the routing, the forms, the responsiveness and the load time. Every entry below links to the running project or its public repository.
For a buyer who wants to see the actual work before deciding whether to start a conversation.
21
Projects in the archive
9
Linked below
0
Invented metrics
Live projects
Open them on a phone. That is how most visitors will see whatever you build next.
Git Pretty View
A web application that renders Git repository statistics, commit history and code contributions as charts and timelines.
Project Manager
A project and task manager with roles, permissions and real-time updates, built on React, Node, Express and MongoDB.
Free Epic Games
Tracks free game promotions and presents them with filtering, search and a history of past offers.
BG Remover
A browser tool that removes image backgrounds client-side, with format options and export.
Package Manager
A dashboard for tracking dependencies across projects and seeing which are out of date.
JustPass Commercial Site
A commercial website presenting services, features and pricing, with backend handling for forms and enquiries.
DNA Technology
A web platform for genetics research and applications, with structured navigation, case studies and responsive layouts.
Command Generator
A VS Code extension that generates boilerplate commands and snippets from user input, with templates and inline previews.
Smooth Motion
A published npm package for smooth scrolling and motion behaviour, installable in any compatible project.
What these projects demonstrate
Different projects, same underlying skills. These are the ones that transfer to client work.
Authentication and roles
The project manager includes user roles and permissions, not just a public page with a login button.
Client-side processing
BG Remover does image work in the browser, which means understanding performance limits rather than throwing a server at the problem.
Commercial presentation
JustPass and DNA Technology are structured to explain an offer clearly, which is the same job a business website does.
Developer tooling
A VS Code extension and an npm package require packaging, versioning and documentation - the unglamorous parts of shipping software.
Responsive by default
Every project is built to work on a phone, because that is where most visitors arrive.
Why there are no traffic, revenue or conversion numbers
Numbers like "increased leads by 240%" are easy to write and almost impossible to verify. They are usually measured over an undefined period, against an undefined baseline, with every other change in the business ignored. Publishing them would make this page look more impressive and less trustworthy at the same time.
What can be verified is whether the software works. Each link above opens a running project. The stack is stated. The feature described is visible. That is a narrower claim than a results metric, and a more useful one for someone deciding whether the developer can build what they need.
When a client project can be documented with real, permissioned numbers - enquiries before and after, with the measurement method stated - it will be added here in that form. Until then, no number is invented to fill the space.
What a client case study will include
The structure is ready. It needs real client work and permission, not filler.
The problem, in the client\u2019s terms rather than the developer\u2019s.
What was built, and what was deliberately left out.
The stack and any notable technical constraint.
A live link, where the client is happy for it to be public.
Measured results only if the client agrees and the method is stated.
A short client quote, in their own words, with permission.
What would be done differently next time - the useful part most portfolios omit.
Projects like these, quoted the same way
A project similar to one above is scoped and priced on its requirements, not on a portfolio tier.
Application or website
A data-heavy app needs models, roles and testing. A marketing site needs structure and content. The quote follows that difference.
Existing systems
Integration with an existing database, payment account or ERP adds discovery and testing that is invisible in a screenshot.
Design and content
A clear brand and ready content shorten the work. Starting from nothing includes more design and writing.
Support and handover
Documentation, training and a support window are included. Ongoing maintenance is optional and priced separately.
Typical timeline
- Landing page or one-page site
- About 1 week
- Business website, 5 to 10 pages
- 2 to 3 weeks
- E-commerce store with payments
- 4 to 8 weeks
- Custom web application or dashboard
- 6 to 12 weeks
- Cross-platform mobile app
- 6 to 10 weeks
Every quote is written for the project in front of me. You get the scope, the milestones, the timeline and the full price before work starts - no hourly surprises and no hidden line items. Send your requirements and the quote comes back free, with no obligation to proceed.
Frequently asked questions
Both. Some were built for clients, others are independent tools and products. They are listed because they are live and inspectable, not to inflate a client count. A client project is never presented as personal work, or the reverse.
Some repositories are public, and a few links above point directly to GitHub or npm. Client projects belong to the client, so their code cannot be shared. For those, the live URL is the evidence.
Because it would be invented. Real metrics need a defined baseline, a measurement period and the client\u2019s permission. None of that exists for these entries, so no number is published. When a client project can be documented that way, it will be.
Yes. The same skills apply: data-heavy interfaces, authentication, dashboards, catalogues and commercial sites. A client project is scoped from its own requirements rather than copied from a portfolio piece.
With permission, yes. Client contact details are never published or passed on without consent, so the request is forwarded rather than answered directly. The reviews page explains the same policy for written feedback.
If you need a store or catalogue, look at JustPass and the shop pages. For a dashboard or internal tool, Git Pretty View and Project Manager. For a mobile app, the app development page describes the React Native work. If none match, describe the requirement and the closest reference will be named honestly.
[email protected] or WhatsApp +91 63834 17749. Edhavadhu project pathi detailed-a kekkalam - stack, approach, enna maaranum.