ShopNest — a project by Ahsan Mahmood
Modern e-commerce platform with comprehensive shopping features
This is the shortest record in the catalogue, and the page is short to match.
ShopNest is an e-commerce platform. Its record lists a product catalogue, a shopping cart, a checkout, order tracking and a payment integration, over React and TypeScript with Tailwind, Firebase underneath and Capacitor for a mobile build. That is the whole of what is written down.
Five features and a stack is not a story, and pretending otherwise is how a portfolio starts lying quietly.
So this page will do something slightly unusual, which is to be honest about its own thinness rather than dressing it. There is a version of this entry that reads well: a paragraph on cart abandonment, another on checkout friction, a confident sentence about payment providers. Every word of it would be generic e-commerce commentary rather than anything about this build, and a reader who has seen three such pages recognises the shape immediately.
What can honestly be said is this.
The feature list is a skeleton. It is the standard shape of a store, in the order a customer meets it. A catalogue to browse, a cart to hold what was chosen, a checkout to turn that into money, tracking so the buyer knows where the parcel is, and a payment integration underneath the whole sequence. Each of those is a real piece of work and none of them is unusual.
The interesting constraint is the one the stack implies.
Firebase on a free tier is a ceiling rather than the absence of one, and a product catalogue is the first surface in any store to meet it. Browsing is the highest-volume read a shop has, it happens before anybody has bought anything, and a catalogue query without an explicit limit becomes a bill drawn by people who are not customers yet. That is the constraint every list read in this codebase would carry.
There is one more fact on the record and it carries more weight than the feature list does.
Its status is in progress.
An e-commerce build has a threshold in it that nothing else in software quite matches: the first time a real person's money moves correctly from their card to somebody's account. Everything before that is a demonstration and everything after it is a business, and a feature list gives no indication which side of the line a project sits on. Naming the status is the only way a reader can tell.
This one is on the near side.
That is stated on the record and it belongs on the page, because the difference between a store that has processed an order and a store that has been designed to matters enormously and is invisible from a feature list. Nothing here claims a launch, a merchant, or a completed checkout.
There is also nowhere to send you.
The links are empty in every slot, and the single candidate address that was probed returns a not-found. That is worth separating from a site being briefly down. A dead candidate means there is no deployment behind the name at all, and the honest response is to name no URL rather than to point at this portfolio's own project index and let a click resolve to something that looks like a product.
The page ends where the record does.
That is not a writing failure. It is the accurate size of what exists, and a longer page would be describing a different project than the one in the database.
What it does, and what that costs to build
- Product catalog
- Shopping cart
- Checkout system
- Order tracking
- Payment integration
Built with
- React
- TypeScript
- Firebase
- TailwindCSS
- CapacitorJS
Worth knowing
- ecommerce
- shopping
- retail
- saas
Who built ShopNest?
Ahsan Mahmood built it, working alone, and it is the thinnest entry in this catalogue for a reason worth stating. Its record carries five features, a stack and nothing else. There is no live address, no listing and no repository, and the one candidate address that was checked returns a not-found rather than a page. So this entry describes what was built and declines to describe what nobody can verify, which is the only honest shape available to it.
Can I look at ShopNest?
No. There is no published address on the record and the one candidate link that was probed answers with a not-found. That is different from a site being temporarily down, and it is different again from a private deployment somebody could be invited to. The page names no URL at all rather than pointing at the portfolio's own project index and letting the click look like a product. An absent link is a fact, not a formatting problem.
What state is it actually in?
In progress, according to its own record, and that status is the most informative thing on it. The catalogue entry lists a product catalogue, a cart, checkout, order tracking and payment integration, which is the standard shape of an e-commerce build rather than an account of how far this one got. Nothing here claims a launch, a merchant or a completed checkout. What exists is the scaffolding of a store, described as scaffolding.
Why does the record say so little?
Because nobody wrote more into it, and this page will not invent the rest. A portfolio entry can be padded from a stack list until it reads like a case study, and the result is a page that sounds informed while resting on nothing. The alternative is a short page that says what the record says, names its absences, and stops. That is the version here, and its brevity is the accurate signal rather than a gap in the writing.
Does ShopNest work on iPhone?
There is no iOS build. The record lists Capacitor in the stack, which is the tool that would package the web application for a phone, but no store listing exists on either platform and no address exists to open in a browser either. There is no Apple Developer account here and nothing I build has shipped to the App Store. On this entry the platform question is academic until there is something running to ask it about.
https://aoneahsan.com/projects/com.aoneahsan.shopnest