<?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: JzaiBaR</title>
    <description>The latest articles on DEV Community by JzaiBaR (@jzaibar).</description>
    <link>https://dev.to/jzaibar</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%2F4223956%2F0f636f60-4902-4b5b-8fab-b37552fb24a2.png</url>
      <title>DEV Community: JzaiBaR</title>
      <link>https://dev.to/jzaibar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jzaibar"/>
    <language>en</language>
    <item>
      <title>What I Check Before I Install Any APK</title>
      <dc:creator>JzaiBaR</dc:creator>
      <pubDate>Wed, 04 Nov 2026 17:55:53 +0000</pubDate>
      <link>https://dev.to/jzaibar/what-i-check-before-i-install-any-apk-3cm8</link>
      <guid>https://dev.to/jzaibar/what-i-check-before-i-install-any-apk-3cm8</guid>
      <description>&lt;p&gt;Sideloading an app is easy. Trusting it is the hard part. My phone holds my bank, my mail, and my family photos.&lt;/p&gt;

&lt;p&gt;First, I check the source page. A clean page shows the version, the size, and the update date. A messy page hides all three.&lt;/p&gt;

&lt;p&gt;Second, I compare the file name. It should match the app name exactly. Extra words in the file name are a bad sign.&lt;/p&gt;

&lt;p&gt;For APK Netfly download pages and version notes, I read the details at &lt;a href="https://apknetfly.com" rel="noopener noreferrer"&gt;Netfly&lt;/a&gt; before I tap install. The page lists what changed in each version.&lt;/p&gt;

&lt;p&gt;Third, I scan the file after download. My antivirus gets the first look. Only then does the installer open.&lt;/p&gt;

&lt;p&gt;Last, I check permissions after install. A flashlight app needs no contacts. If the list looks wrong, the app goes.&lt;/p&gt;

</description>
      <category>android</category>
      <category>beginners</category>
      <category>security</category>
    </item>
    <item>
      <title>Inches, Centimetres and the CSS Nobody Agrees On</title>
      <dc:creator>JzaiBaR</dc:creator>
      <pubDate>Tue, 03 Nov 2026 09:51:32 +0000</pubDate>
      <link>https://dev.to/jzaibar/inches-centimetres-and-the-css-nobody-agrees-on-27n4</link>
      <guid>https://dev.to/jzaibar/inches-centimetres-and-the-css-nobody-agrees-on-27n4</guid>
      <description>&lt;p&gt;Every front-end developer has lost an afternoon to a screen that was "27 inches" in the listing, 68.6 cm in the spec sheet, and somehow a different physical size on the desk. Physical units and CSS units live in different worlds, and confusing them is a rite of passage.&lt;/p&gt;

&lt;p&gt;The physical side is simple. One inch is exactly 2.54 cm — defined, not measured. A 27-inch monitor is 68.58 cm diagonally, a 6.1-inch phone is 15.49 cm. When you are comparing hardware, checking whether a monitor fits a desk gap, or reading a US product page from a metric country, an &lt;a href="https://pulgadas-a-cm.org" rel="noopener noreferrer"&gt;inches to cm converter&lt;/a&gt; settles it in one step: inches × 2.54, done.&lt;/p&gt;

&lt;p&gt;The CSS side is where it gets weird. A CSS inch (in) is not a physical inch. CSS defines 1in = 96px exactly, anchored to a reference pixel — so on most screens a "2in" element is nowhere near two physical inches. The same goes for CSS cm and mm: they are just scaled fractions of that 96px inch (1cm = 37.8px), useful for print stylesheets, misleading for anything on a desk.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Practical rules that save time.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Hardware and furniture: true units — convert with ×2.54 and trust the tape measure.&lt;/li&gt;
&lt;li&gt;Screen layouts: pixels, rem and percentages — never physical units.&lt;/li&gt;
&lt;li&gt;Print stylesheets: CSS cm/mm are fine, because the printer pipeline actually honours them.&lt;/li&gt;
&lt;li&gt;Buying from US stores: assume listings are inches; convert before you commit, especially for monitor arms, TV mounts and cases, where "close enough" means a return shipment.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two worlds, two rulebooks. Keep the physical conversions exact and the CSS ones relative, and neither will bite you again.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
