<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sabbir Hasan</title>
    <description>The latest articles on DEV Community by Sabbir Hasan (@stropurbo).</description>
    <link>https://dev.to/stropurbo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4205773%2F87bbfc8b-8bc6-4ec0-8861-33b01f39d517.png</url>
      <title>DEV Community: Sabbir Hasan</title>
      <link>https://dev.to/stropurbo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/stropurbo"/>
    <language>en</language>
    <item>
      <title>Barcode vs Manual Logging: What Actually Keeps Beginners Tracking</title>
      <dc:creator>Sabbir Hasan</dc:creator>
      <pubDate>Tue, 03 Nov 2026 14:23:03 +0000</pubDate>
      <link>https://dev.to/stropurbo/barcode-vs-manual-logging-what-actually-keeps-beginners-tracking-a63</link>
      <guid>https://dev.to/stropurbo/barcode-vs-manual-logging-what-actually-keeps-beginners-tracking-a63</guid>
      <description>&lt;p&gt;Most people don't quit calorie tracking because they don't care about their health. They quit because logging a meal feels like homework. I learned this building CalyFit, a free calorie tracker aimed at beginners and busy people — and the barcode scanner versus manual entry debate turned out to be less about technology and more about friction.&lt;/p&gt;

&lt;p&gt;Here is the honest version of what works, what doesn't, and how to design logging so people actually stick with it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The real enemy is friction, not willpower
&lt;/h2&gt;

&lt;p&gt;A beginner opening a calorie app for the first time faces two questions: "What did I just eat?" and "How much effort will it take to record it?" If the second answer is "a lot," the first question stops mattering. People skip the entry, then skip the day, then quietly delete the app.&lt;/p&gt;

&lt;p&gt;That is why the simplest tracking wins. Not the most detailed tracking — the tracking that survives a busy Tuesday. Every extra tap, search, and guess is a chance to quit. Design for the tired version of your user, not the motivated one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where barcode scanning shines
&lt;/h2&gt;

&lt;p&gt;Barcode scanning is the lowest-friction entry point we have, and it is genuinely great for packaged food. Point the camera at a packet of biscuits, a yoghurt tub, or a box of cereal, and the item appears with its calories and macros already filled in. No searching, no guessing portion sizes from a long list of near-identical results.&lt;/p&gt;

&lt;p&gt;For beginners, that instant success matters. The first log should feel like a win, not a test. Scanning gives that win in seconds, and it teaches something useful along the way: people start noticing what is actually in the food they buy every week.&lt;/p&gt;

&lt;p&gt;But barcode scanning has a hard limit, and pretending otherwise would be dishonest. It does not help with the food that matters most to many people: home-cooked meals, street food, restaurant plates, and anything without a packet. If your app only works well for packaged food, it only works well for part of real life.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where manual logging earns its place
&lt;/h2&gt;

&lt;p&gt;Manual logging gets a bad reputation because most apps make it painful: endless search results, confusing portion units, and databases full of entries nobody verified. Done simply, though, manual entry is the only way to cover real meals.&lt;/p&gt;

&lt;p&gt;The trick is to keep it small. A short search, sensible defaults, and portion options in plain language — a bowl, a plate, a piece — beat a precise gram field that nobody fills in honestly. A roughly right entry logged today beats a perfectly accurate entry that never happens.&lt;/p&gt;

&lt;p&gt;Manual logging also builds a skill barcode scanning never will: estimation. After a few weeks of logging home meals, people get better at judging portions without the app. That is the point. The app should make itself less necessary over time, not more addictive.&lt;/p&gt;

&lt;h2&gt;
  
  
  The combination that actually sticks
&lt;/h2&gt;

&lt;p&gt;In CalyFit, the two methods are not rivals — they cover each other's gaps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Scan when you can. Packaged food, snacks, drinks — scan it and move on.&lt;/li&gt;
&lt;li&gt;Log simply when you can't. Home meals and eating out get a quick manual entry with macros, not a research project.&lt;/li&gt;
&lt;li&gt;Track the rest of the day lightly. Steps, water, and sleep sit alongside food, so one missed meal log doesn't feel like a failed day.&lt;/li&gt;
&lt;li&gt;Set a goal that fits real life. BMI and personalized goals give beginners a target without demanding perfection from day one.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Voice logging helps here too — speaking a meal out loud is faster than typing it when your hands are busy. The theme is the same throughout: fewer taps, less typing, more days logged.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I would tell any developer building a tracker
&lt;/h2&gt;

&lt;p&gt;If you are building a health or habit app, steal these lessons:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Measure the second entry, not the first. Anyone can log once. The question is whether logging still feels easy on day fourteen.&lt;/li&gt;
&lt;li&gt;Default to the easy path. Put the scanner and the quick search where thumbs already go. Bury the advanced options.&lt;/li&gt;
&lt;li&gt;Forgive gaps. A missed day should never feel like a broken streak worth abandoning. Let people come back without guilt.&lt;/li&gt;
&lt;li&gt;Show progress, not just data. Macros, steps, water, and sleep mean more when users can see a week getting steadier, not just a single number going up or down.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Beginners don't need more features. They need fewer reasons to stop.&lt;/p&gt;

&lt;h2&gt;
  
  
  The takeaway
&lt;/h2&gt;

&lt;p&gt;Barcode scanning wins on speed. Manual logging wins on coverage. A tracker that respects beginners offers both, keeps both simple, and never punishes an imperfect day. That is how a free, simple app earns a place in someone's routine — one low-friction meal at a time.&lt;/p&gt;

&lt;p&gt;Try CalyFit on Google Play: &lt;a href="https://play.google.com/store/apps/details?id=com.sabbir.myboguraa" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.sabbir.myboguraa&lt;/a&gt; — or see all my apps: &lt;a href="https://c8ke.com/stropurbo" rel="noopener noreferrer"&gt;https://c8ke.com/stropurbo&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>fitness</category>
      <category>health</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Why Your Phone-to-TV Mirror Lags — and How to Fix It</title>
      <dc:creator>Sabbir Hasan</dc:creator>
      <pubDate>Fri, 30 Oct 2026 14:27:55 +0000</pubDate>
      <link>https://dev.to/stropurbo/why-your-phone-to-tv-mirror-lags-and-how-to-fix-it-52o7</link>
      <guid>https://dev.to/stropurbo/why-your-phone-to-tv-mirror-lags-and-how-to-fix-it-52o7</guid>
      <description>&lt;p&gt;You tap "cast," your phone screen appears on the TV — and then it stutters. The video freezes for a second, the audio drifts out of sync, and a game that felt smooth on your phone turns unplayable on the big screen. If you have ever mirrored your phone to a TV, you have met this problem.&lt;/p&gt;

&lt;p&gt;I build TV Cast, an Android app for casting a phone screen to a TV. Fixing lag was the biggest part of making it feel usable, and most fixes had nothing to do with clever code. They were about the connection between phone and TV. Here is what I learned.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lag has three sources, not one
&lt;/h2&gt;

&lt;p&gt;When people say "mirroring lags," they usually mean one of three different things, and each has a different fix.&lt;/p&gt;

&lt;p&gt;First, network delay: the time it takes each frame to travel from your phone to your TV over Wi-Fi. Second, encoding delay: your phone has to compress every frame before sending it, which costs processor time. Third, display delay: the TV itself takes time to process and show the incoming picture, especially with motion smoothing or game mode turned off.&lt;/p&gt;

&lt;p&gt;If you fix the wrong one, nothing improves. A faster phone will not help a congested Wi-Fi network, and a better router will not help a TV stuck in a slow picture mode. So start by finding which bottleneck you actually have.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your Wi-Fi band matters more than your internet speed
&lt;/h2&gt;

&lt;p&gt;This surprises most people: mirroring lag usually has nothing to do with your internet plan. When you cast over Chromecast, AirPlay, or Miracast, the video travels over your local network, not the internet. A 500 Mbps broadband plan will not save a crowded 2.4 GHz Wi-Fi channel.&lt;/p&gt;

&lt;p&gt;The 2.4 GHz band is crowded. Neighbouring routers, Bluetooth devices, and even microwaves compete for the same airspace. The 5 GHz band is faster and far less congested, but its range is shorter. If your phone and TV can both reach your router on 5 GHz, switch them to it. That single change fixes more lag complaints than anything else I have seen.&lt;/p&gt;

&lt;p&gt;Distance matters too. If the router sits two rooms away behind a wall, every frame fights for signal. Moving the router closer to the TV, or the TV closer to the router, often beats any software setting.&lt;/p&gt;

&lt;h2&gt;
  
  
  Close the apps you forgot about
&lt;/h2&gt;

&lt;p&gt;Encoding delay is the hidden culprit on older or mid-range phones. Mirroring asks your phone to do two jobs at once: run whatever you are showing, and compress its screen in real time. If ten apps are running in the background, syncing, uploading photos, or refreshing feeds, they steal both processor time and Wi-Fi bandwidth.&lt;/p&gt;

&lt;p&gt;Before an important cast — a presentation, a movie night, a gaming session — close background apps and pause cloud backups and large downloads. It sounds too simple to matter, but on a busy phone it can be the difference between smooth video and a slideshow.&lt;/p&gt;

&lt;p&gt;Screen recording is another load worth knowing about. Recording while mirroring means the phone encodes the screen twice over. If you need a recording, capture it separately when you can, rather than stacking both jobs at once.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pick the right path to the TV
&lt;/h2&gt;

&lt;p&gt;Not every TV receives a cast the same way, and the best route depends on what you own. Chromecast built-in, Miracast, and AirPlay each behave differently on different networks, and a phone that struggles on one route may run smoothly on another. If your first attempt stutters, trying a different supported receiver on the same TV is a legitimate troubleshooting step, not a superstition.&lt;/p&gt;

&lt;p&gt;The same logic applies to what you are casting. A static presentation slide is easy: almost nothing changes between frames, so the encoder has little work to do. Fast-moving games and sports are the hardest test, because every frame changes completely. If games lag but slides do not, your bottleneck is encoding or bandwidth, not a broken app.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the TV's own settings
&lt;/h2&gt;

&lt;p&gt;TVs add delay of their own. Motion smoothing features, which make movies look unnaturally fluid, add processing time to every frame. Game mode, where your TV has one, usually cuts that processing to a minimum and is worth turning on even when you are not gaming — it is often simply the lowest-latency mode the TV offers.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick checklist before you cast
&lt;/h2&gt;

&lt;p&gt;Here is the routine I now recommend, in order:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Put the phone and the TV on the 5 GHz Wi-Fi band if you can.&lt;/li&gt;
&lt;li&gt;Move closer to the router, or the router closer to the TV.&lt;/li&gt;
&lt;li&gt;Close background apps and pause downloads and backups.&lt;/li&gt;
&lt;li&gt;Turn on game mode on the TV, and turn off motion smoothing.&lt;/li&gt;
&lt;li&gt;If one casting route stutters, try another supported receiver on the same TV.&lt;/li&gt;
&lt;li&gt;For games, keep the phone charged and cool — a hot, throttling phone encodes slower.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Most lag disappears somewhere in those six steps. What remains is usually a genuine hardware limit: a very old phone, a very old TV, or a network stretched across too many walls. Knowing that is useful too, because it stops you chasing settings that were never the problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this matters beyond movie night
&lt;/h2&gt;

&lt;p&gt;Mirroring is no longer a novelty. People present from their phones in meetings, show photos to family on the big screen, and play mobile games on a TV with friends. Each of those uses breaks the moment lag appears. The fix is rarely one dramatic change — it is a handful of small, boring ones, applied in the right order.&lt;/p&gt;

&lt;p&gt;That is the lesson building a casting app taught me: users do not experience "the protocol" or "the codec." They experience whether the picture keeps up with their hands.&lt;/p&gt;

&lt;p&gt;Try TV Cast on Google Play: &lt;a href="https://play.google.com/store/apps/details?id=com.sabbir.tvcastscreenmirroring" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.sabbir.tvcastscreenmirroring&lt;/a&gt; — or see all my apps: &lt;a href="https://c8ke.com/stropurbo" rel="noopener noreferrer"&gt;https://c8ke.com/stropurbo&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>screenmirroring</category>
      <category>tv</category>
      <category>apps</category>
    </item>
    <item>
      <title>Why Simple Tracking Beats Feature-Heavy Fitness Apps</title>
      <dc:creator>Sabbir Hasan</dc:creator>
      <pubDate>Tue, 27 Oct 2026 14:23:46 +0000</pubDate>
      <link>https://dev.to/stropurbo/why-simple-tracking-beats-feature-heavy-fitness-apps-jfp</link>
      <guid>https://dev.to/stropurbo/why-simple-tracking-beats-feature-heavy-fitness-apps-jfp</guid>
      <description>&lt;p&gt;Most fitness apps fail beginners in the same quiet way. They do not fail because they lack features. They fail because they have too many.&lt;/p&gt;

&lt;p&gt;Open a typical calorie tracker for the first time and you meet a dashboard full of charts, a meal database with a thousand options, a workout library, a social feed, and a premium upsell before you have logged a single meal. For someone who just wants to eat a little better, that first screen already feels like homework. Many people close the app and never come back.&lt;/p&gt;

&lt;p&gt;I built CalyFit for the opposite kind of person: busy people and beginners who want the simplest possible way to track what they eat and how they move. That focus on simplicity changed every product decision, and it taught me something worth sharing with other builders: in health apps, less is not a compromise. Less is the feature.&lt;/p&gt;

&lt;h2&gt;
  
  
  The paradox of more features
&lt;/h2&gt;

&lt;p&gt;Every extra feature looks good in a planning meeting. In real life, every extra feature is also an extra decision, an extra tap, and an extra reason to quit on a busy day.&lt;/p&gt;

&lt;p&gt;A beginner does not wake up thinking, "I need advanced nutrient timing." They think, "I ate too much yesterday, and I want today to be better." If the app cannot help with that thought in under a minute, the rest of its features do not matter.&lt;/p&gt;

&lt;p&gt;Simple tracking wins because it survives bad days. On a good day, anyone can log a perfect meal. On a tired, rushed day, only a simple flow survives: open, log, done. The habit matters more than the data.&lt;/p&gt;

&lt;h2&gt;
  
  
  What beginners actually need
&lt;/h2&gt;

&lt;p&gt;After watching how beginners use a tracker, the real needs are surprisingly small:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A fast way to log food, without typing a full recipe.&lt;/li&gt;
&lt;li&gt;A clear daily picture: calories, protein, carbs, and fat at a glance.&lt;/li&gt;
&lt;li&gt;Movement that counts without extra work, like steps.&lt;/li&gt;
&lt;li&gt;A few basics that shape the day: water, sleep, and a realistic goal.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That is it. Everything else is optional, and most of it can wait until the habit is already strong.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I kept in CalyFit
&lt;/h2&gt;

&lt;p&gt;CalyFit is a free Android app built around that short list. It keeps logging fast in three ways: scan a barcode when the food has one, type a quick manual entry when it does not, or use voice logging when your hands are busy. You see your macros for the day without digging through menus. Steps, water, and sleep sit in the same place as your food, because a day of health is one picture, not five separate apps.&lt;/p&gt;

&lt;p&gt;It also sets a personalized goal from your BMI and your target, so a beginner does not have to guess their numbers on day one. And if you already use Google Fit, it syncs with it, so steps you already walked still count.&lt;/p&gt;

&lt;p&gt;None of this is flashy. That is the point. The best health feature is the one you actually use on a Tuesday night when you are tired.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I deliberately left out
&lt;/h2&gt;

&lt;p&gt;Saying no was the hardest part of building. It is tempting to add a feature every time someone asks for one. But each addition makes the app heavier for the next beginner who opens it for the first time.&lt;/p&gt;

&lt;p&gt;So CalyFit stays focused on simple daily tracking for busy people and beginners. No maze of menus. No ten-step setup. No feature you need a tutorial to understand. If a feature does not make logging faster or the daily picture clearer, it does not earn its place.&lt;/p&gt;

&lt;p&gt;Builders often measure progress by what they shipped. For a beginner-focused app, a better measure is what a new user can do in the first five minutes without help.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to start in five minutes
&lt;/h2&gt;

&lt;p&gt;If you are starting from zero, here is the simplest version that works:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Log just one meal today, not the whole day. A partial log beats a perfect plan you never start.&lt;/li&gt;
&lt;li&gt;Check your macros once in the evening, not after every bite.&lt;/li&gt;
&lt;li&gt;Let steps count automatically instead of adding a workout you will skip.&lt;/li&gt;
&lt;li&gt;Drink a glass of water and note it. Small wins build the habit.&lt;/li&gt;
&lt;li&gt;Repeat tomorrow. The streak is the system.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You do not need a perfect week. You need a repeatable day.&lt;/p&gt;

&lt;h2&gt;
  
  
  Takeaways for builders and beginners
&lt;/h2&gt;

&lt;p&gt;For builders: design the first session, not the hundredth feature. If a beginner cannot log a meal in a minute, fix that before adding anything new.&lt;/p&gt;

&lt;p&gt;For beginners: pick the simplest tracker you will actually open. A simple app used daily beats a powerful app opened twice.&lt;/p&gt;

&lt;p&gt;Simplicity is not about doing less work. It is about doing the right work, in the right order, and leaving everything else out until the habit is strong enough to carry it.&lt;/p&gt;

&lt;p&gt;Try CalyFit on Google Play: &lt;a href="https://play.google.com/store/apps/details?id=com.sabbir.myboguraa" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.sabbir.myboguraa&lt;/a&gt; — or see all my apps: &lt;a href="https://c8ke.com/stropurbo" rel="noopener noreferrer"&gt;https://c8ke.com/stropurbo&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>fitness</category>
      <category>health</category>
      <category>beginners</category>
    </item>
    <item>
      <title>I Built a Calorie Tracker for Beginners — Here's What Simplicity Taught Me</title>
      <dc:creator>Sabbir Hasan</dc:creator>
      <pubDate>Sun, 25 Oct 2026 03:52:20 +0000</pubDate>
      <link>https://dev.to/stropurbo/i-built-a-calorie-tracker-for-beginners-heres-what-simplicity-taught-me-aei</link>
      <guid>https://dev.to/stropurbo/i-built-a-calorie-tracker-for-beginners-heres-what-simplicity-taught-me-aei</guid>
      <description>&lt;p&gt;Most calorie tracking apps fail beginners in the first week. Not because people lack discipline, but because the apps ask for too much: weigh every gram, search through endless food databases, and decode charts before you have even finished your first day.&lt;/p&gt;

&lt;p&gt;I built CalyFit around the opposite idea: the simplest calorie tracking for busy people and beginners. Here is what building it taught me.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Every extra tap loses a user
&lt;/h2&gt;

&lt;p&gt;The first version of my food log had portion sizes, cooking methods, and half a dozen optional fields. Testers skipped logging entirely. When I cut logging down to the essentials — pick the food, confirm the portion, done — people actually kept going.&lt;/p&gt;

&lt;p&gt;Lesson: for beginners, a good-enough entry today beats a perfect entry never made.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Barcode beats typing
&lt;/h2&gt;

&lt;p&gt;Typing "chicken sandwich" into a search box and picking from fifty near-identical results is friction. Scanning a barcode and getting the item instantly is not. That one interaction changed how often people logged. If you are building any kind of tracker, find the one input your users repeat daily and make it nearly free.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Habits beat perfection
&lt;/h2&gt;

&lt;p&gt;Nobody eats perfectly, and an app that makes you feel guilty about it gets deleted. CalyFit tracks the basics that keep people going: calories and macros, daily steps, water and sleep, plus BMI and personalized goals. A short daily streak of "I logged today" does more for a beginner than any advanced analytics dashboard.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Build in public with zero budget
&lt;/h2&gt;

&lt;p&gt;CalyFit was built and marketed with a $0 budget. It is rated 4.3 stars on Google Play, and every bit of growth so far came from consistent, honest content rather than ads. Building in public forced me to be honest about what the app does and does not do — and users trust that more than polished marketing.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I would do differently
&lt;/h2&gt;

&lt;p&gt;I would have talked to beginners before writing a single line of code. I assumed people wanted more features. They wanted fewer, clearer ones. If you are building your first app, find five people in your target audience and watch them use a rough version. Their confusion is your roadmap.&lt;/p&gt;

&lt;h2&gt;
  
  
  The takeaway
&lt;/h2&gt;

&lt;p&gt;Simplicity is not a lack of features. It is a decision about which friction to remove first. For a beginner, the best tracking app is the one they still open in week three.&lt;/p&gt;

&lt;p&gt;Try CalyFit on Google Play: &lt;a href="https://play.google.com/store/apps/details?id=com.sabbir.myboguraa" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.sabbir.myboguraa&lt;/a&gt; — or see all my apps: &lt;a href="https://c8ke.com/stropurbo" rel="noopener noreferrer"&gt;https://c8ke.com/stropurbo&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>fitness</category>
      <category>health</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
