About Primetimetrade
Primetimetrade exists to answer one practical question: once you've decided to make a particular snack, chaat, or street-food dish, what do you actually need to know to get it right on the first attempt? The library is built around that question — recipes with real measurements, technique guides for the steps that trip people up, and regional notes that explain why a dish is made one way in one city and differently somewhere else.
The purpose behind the finder
The point here isn't to pile up the longest possible list of recipes. It's to make sure each one, taken on its own, gives you enough to actually work from: exact quantities instead of a vague gesture, equipment lists that only include what a step genuinely requires, the reasoning behind a tricky technique, and the regional background that explains why a dish tastes the way it does. Because that list of recipes grows fast, the library runs through a finder you can filter by diet, time, difficulty, cooking method, main ingredient, region, snack type and spice level — so you search by whatever matters to you first, rather than scrolling through everything in order. In short: depth within each recipe, and a quick way to reach the one you want.
Why recipes are written the way they are
Start from the assumption that a recipe should be cooked from, not just admired on a screen. That's why quantities are given as real numbers rather than vague gestures, why an equipment list only includes what a step genuinely needs, and why each method is broken into stages meant to be followed in order. When a dish changes meaningfully from one household or region to the next, that variation gets named here rather than papered over by picking a single version and calling it definitive.
Guides sit next to the recipes for a reason, not as an afterthought. Batters, chutneys, frying and tempering keep reappearing across dishes that otherwise look nothing alike, so understanding one of these techniques properly, once, makes every recipe built on it faster to cook with confidence.
How origin and region are handled
Treat India's snack and street-food traditions as one single national cuisine, and you lose almost everything interesting about them — they're really a set of distinct regional traditions, shaped by different cities, states, climates and histories. A dish that grew up around Mumbai's railway stalls, one tied to Delhi's winter markets, and one that belongs to a Gujarati household are kept as separate stories here, not folded into one generic description of "Indian food." Several chaat dishes in particular have origins claimed by more than one region; where that's the case, the disagreement itself gets described rather than quietly settled in favor of one version. The same caution applies to historical claims more broadly: an account that can't be verified is presented as a commonly told story, never as settled fact.
What's deliberately left out
- Invented numbers. No calorie counts or nutrition figures get attached to a dish unless they've been independently sourced and verified, because a guessed-at number dressed up as fact does more harm than no number at all.
- Health claims dressed up as medicine. An ingredient having a long history of traditional use is a cultural fact, not a clinical one, and the two are kept separate on every page.
- Reviews or quotes nobody actually said. Star ratings, testimonials and quotes attributed to a cook or chef don't appear here unless they trace back to a real, checkable source.
- Shortcuts that compromise safety, including unsafe reuse of frying oil or any shortcut around the safe handling of meat, dairy or fried food.
When something's wrong
Every recipe and regional note gets checked before it goes up, but checking isn't the same thing as infallible, and some culinary history is genuinely argued over even among people who grew up eating the dish. If a page here looks off, incomplete, or could use a better source, the Corrections page walks through exactly how to flag it.