Urgent.News

What's breaking now, across thousands of outlets.

Tech

I track protein, not calories. So I built a dead-simple tracker for lifters.

Every food-tracking app wants the same things from me: calories, macros, a subscription, an account, a barcode-scanning onboarding flow. I'm a lifter. I don't care about any of that. I care about one number: did I hit my protein today? Protein Pal is the tracker that asks exactly one question. Log what you ate with its protein grams, and watch the big daily total climb toward your goal — default…

I focused on one metric only: protein intake. My tracker, Protein Pal, asks just one question: Did you reach your protein goal today? To use it, log the foods you ate, specifying their protein grams. A daily total climbs toward your objective—180 grams by default, but you can change it.

Logging is quick and simple: tap once to add an item. Recent foods, like your daily chicken breast, can be accessed with a single tap. The progress bar visibly tracks your progress, while per-day history shows your daily totals. All of this works offline, without accounts or servers, directly from your browser. It was created for the Devpost Build With AI: Basics hackathon, following a plan-first approach: sketching the idea, outlining the product requirements, developing a technical specification, and then coding.

The simplicity of protein tracking is the core focus, with no calorie counting, macros, accounts, or social features. If you're looking for an easy way to monitor your protein intake, Protein Pal offers a straightforward solution.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Yatta JS launches Sunday, October 4

Quick heads up for the weekend. I am releasing Yatta JS on Sunday, October 4. It is a backend runtime for Bun that embeds the whole stack in your app process: relational DB, passkeys and MFA auth…

Summing RSS Is Not Your WSL2 Memory Usage

Task Manager says "VmmemWSL" is holding 8 GB, while inside Ubuntu, "htop" shows something closer to 2 GB. At first, the difference is difficult to interpret because both numbers look perfectly…

  • Task Manager shows 8 GB memory used by VmmemWSL
  • Htop inside Ubuntu reports around 2 GB memory usage
  • RSS values from multiple processes do not equal WSL2 memory usage

Debug Blurry Compressed PDF Images — 4 Resolution Checks Before Watermarking

TL;DR: When a compressed PDF looks blurry, debug embedded image resolution before changing compression settings. Keep the archival PDF unchanged, own the watermark template, and generate a separate…

  • Verify source image pixel dimensions and intended placement size
  • Examine template owner's behavior for stability in disclosure rules
  • Run four TypeScript preflight tests before watermarking

More from Thursday 1 October →