Waqar Anwar

Today someone bought NFL's lifetime deal, the first one ever. NFL is built by one person, so this one means a lot. Thank you, whoever you are.

A lifetime deal is a real vote of trust. You're betting the tool will still be here and still be useful years from now. I take that seriously, and I'll keep the label rules up to date as regulations change, with every format still citing the paragraph it follows.

Thanks also to everyone here who tried NFL, left a review or sent feedback. I've read every review, including the requests for more branding options and bulk export.

If you sell food in more than one market, I'd love to hear which label format you need next.

Users of a focused tool naturally ask for the next thing next door and often they already have the data in your product to do it. Saying yes feels like listening. Saying yes ten times is how a sharp tool becomes a bloated one that does everything adequately and nothing well.

The tempting version is when the adjacent feature uses the exact data the user already entered, to answer the very next question they were about to ask elsewhere. That feels less like creep and more like finishing the job. But that is also what every scope-creep decision feels like from the inside.

There is one directory in my project I am not allowed to refactor, even to tidy it up: the code that draws the actual Nutrition Facts panel, to the regulator's spacing rules.

It is not pretty code. But it is correct, it is verified against the regulation's worked examples, and every "improvement" I can imagine risks nudging a hairline rule by half a point and making thousands of generated labels subtly non-compliant. So it is frozen. Bugs elsewhere get fixed; that folder gets read-only respect.