<?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: seo seo</title>
    <description>The latest articles on DEV Community by seo seo (@seo_seo_ee802f09cf450729f).</description>
    <link>https://dev.to/seo_seo_ee802f09cf450729f</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%2F4215459%2Fb39f63ad-ea47-41ca-b53a-a4b0d27ab38a.png</url>
      <title>DEV Community: seo seo</title>
      <link>https://dev.to/seo_seo_ee802f09cf450729f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/seo_seo_ee802f09cf450729f"/>
    <language>en</language>
    <item>
      <title>Making dashboard cards survive font scale 1.3 and density 560 on Android</title>
      <dc:creator>seo seo</dc:creator>
      <pubDate>Tue, 03 Nov 2026 13:00:00 +0000</pubDate>
      <link>https://dev.to/seo_seo_ee802f09cf450729f/making-dashboard-cards-survive-font-scale-13-and-density-560-on-android-1ang</link>
      <guid>https://dev.to/seo_seo_ee802f09cf450729f/making-dashboard-cards-survive-font-scale-13-and-density-560-on-android-1ang</guid>
      <description>&lt;p&gt;A dashboard screen is a stack of fixed-size cards: a big clock, a weather card, a countdown, a month calendar. It looks right on my test phone, and then someone sets the system font to Large or runs a denser display, and text spills out of the cards. This is what I changed in my Android flip-clock app (Kotlin and XML) to stop that.&lt;/p&gt;

&lt;h2&gt;
  
  
  The two settings I test with
&lt;/h2&gt;

&lt;p&gt;Both can be changed from adb, so every layout change gets checked at the extremes:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;adb shell wm density 560
adb shell settings put system font_scale 1.3
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After testing I put the device back with &lt;code&gt;wm density 420&lt;/code&gt; and &lt;code&gt;font_scale 1.0&lt;/code&gt;. It is easy to forget, and then every screenshot afterwards is wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 1: card text in dp, not sp
&lt;/h2&gt;

&lt;p&gt;On the dashboard the cards have a fixed size. If their text is in &lt;code&gt;sp&lt;/code&gt;, a larger system font makes the text outgrow the card. So the text inside the dashboard cards uses &lt;code&gt;dp&lt;/code&gt;, and the system font scale no longer changes it.&lt;/p&gt;

&lt;p&gt;The trade-off is real: those cards ignore the user's font-size preference. I accepted it because the cards show short, glanceable values (a temperature, a day count) rather than paragraphs, and an overflowing card is worse than a card that keeps its size.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 2: a separate landscape layout for the tightest card
&lt;/h2&gt;

&lt;p&gt;The weather card has to show a required attribution: a logo plus a line of text. On short screens it was cut off, in portrait and in landscape. Two changes fixed it: the card's text is sized in dp, and landscape got its own, more compact layout (&lt;code&gt;layout-land/&lt;/code&gt;) where the attribution sits in one row.&lt;/p&gt;

&lt;p&gt;The cost is that the two layouts have to be kept in sync by hand. I wrote that into the project notes so I don't forget.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 3: clipping you only see on a zoomed screenshot
&lt;/h2&gt;

&lt;p&gt;A small gear button on the countdown card looked fine until I zoomed in: its top and right edges were cut off. The button overlaps the card's 14dp padding, and a parent clips its children to its padding by default (&lt;code&gt;clipToPadding&lt;/code&gt; is true). Setting &lt;code&gt;clipToPadding="false"&lt;/code&gt; on the card's root fixed it. I only found it because I zoomed into screenshots of every card instead of glancing at the whole screen.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;Test at the extremes first, not at the end.&lt;/li&gt;
&lt;li&gt;Zoom into each card. Whole-screen screenshots hide small clipping.&lt;/li&gt;
&lt;li&gt;Write down which layouts must be changed together.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I'd like to hear
&lt;/h2&gt;

&lt;p&gt;How do you handle fixed-size cards and large system fonts? If you keep sp, do you let cards grow instead? I'd like to compare approaches.&lt;/p&gt;

</description>
      <category>android</category>
      <category>kotlin</category>
      <category>mobile</category>
      <category>ux</category>
    </item>
    <item>
      <title>Submitting your first Android app to Google Play: the paperwork nobody warns you about</title>
      <dc:creator>seo seo</dc:creator>
      <pubDate>Sat, 31 Oct 2026 04:25:42 +0000</pubDate>
      <link>https://dev.to/seo_seo_ee802f09cf450729f/submitting-your-first-android-app-to-google-play-the-paperwork-nobody-warns-you-about-7l4</link>
      <guid>https://dev.to/seo_seo_ee802f09cf450729f/submitting-your-first-android-app-to-google-play-the-paperwork-nobody-warns-you-about-7l4</guid>
      <description>&lt;p&gt;I spent less calendar time writing my first Android app than getting it through Google Play Console. Here is the checklist I wish I had, based on shipping a small flip-clock app (Kotlin and XML, no extra SDKs).&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Graphics have strict specs
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;App icon: 512x512, PNG or JPEG, up to 1 MB&lt;/li&gt;
&lt;li&gt;Feature graphic: 1024x500, up to 15 MB&lt;/li&gt;
&lt;li&gt;Phone screenshots: 2 to 8 images, PNG or JPEG, up to 8 MB each, aspect ratio 16:9 or 9:16, each side 320 to 3840 px&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;My screenshots came straight from the device at 2:1, which doesn't fit. Instead of cropping the UI, I scaled them down and padded the sides with the screen's background color to reach 1080x1920.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. The listing has hard limits
&lt;/h2&gt;

&lt;p&gt;App name 30 characters, short description 80, full description 4,000. I picked the name for search ("Flip Clock: Weather &amp;amp; Calendar") and kept my brand in the developer name.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Data safety: "collected" vs "shared"
&lt;/h2&gt;

&lt;p&gt;My app makes one optional network call: weather, using approximate location. Location that leaves the device counts as collected. Whether it is also shared depends on whether the provider counts as a service provider acting on your behalf. I answered conservatively ("shared"), because over-declaring doesn't get rejected while under-declaring can.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. The privacy policy must match the app
&lt;/h2&gt;

&lt;p&gt;You need a public URL. I host mine on GitHub Pages and updated it when I added the weather feature. The policy, the Data safety answers and the listing text all have to tell the same story.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Content rating is a questionnaire
&lt;/h2&gt;

&lt;p&gt;It is an IARC questionnaire and the rating comes from your answers. For a clock with no user-generated content, every answer was "no".&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Attribution and licences
&lt;/h2&gt;

&lt;p&gt;If you use a data API, read its attribution rules. OpenWeather's free plan asks for visible attribution, and a link buried in a legal page isn't enough. I also ship an open-source licences screen inside the app.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Signing and versions
&lt;/h2&gt;

&lt;p&gt;Upload an AAB signed with your upload key. versionCode has to go up with every upload. Keep the keystore out of git.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. The testing requirement depends on your account
&lt;/h2&gt;

&lt;p&gt;New personal developer accounts may need a closed test with 12 testers for 14 days before production. My account is older and wasn't affected, so check what your own Console dashboard says before you plan around it.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. Review takes a while
&lt;/h2&gt;

&lt;p&gt;After the first submission the dialog said review usually finishes within 7 days. Later listing changes, like adding translations, go through review too.&lt;/p&gt;

&lt;p&gt;What did I miss? If you have shipped an app, I'd like to hear which step cost you the most time.&lt;/p&gt;

</description>
      <category>android</category>
      <category>beginners</category>
      <category>mobile</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>I built a calm flip clock for Android (weather, calendar, D-Day, Pomodoro)</title>
      <dc:creator>seo seo</dc:creator>
      <pubDate>Thu, 29 Oct 2026 13:50:46 +0000</pubDate>
      <link>https://dev.to/seo_seo_ee802f09cf450729f/i-built-a-calm-flip-clock-for-android-weather-calendar-d-day-pomodoro-22oj</link>
      <guid>https://dev.to/seo_seo_ee802f09cf450729f/i-built-a-calm-flip-clock-for-android-weather-calendar-d-day-pomodoro-22oj</guid>
      <description>&lt;p&gt;I wanted a quiet clock for my desk, so I built one: &lt;strong&gt;Flip Clock: Weather &amp;amp; Calendar&lt;/strong&gt;, a flip clock for Android with weather, a monthly calendar, a D-Day counter and a Pomodoro timer.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Flip-Dashboard:&lt;/strong&gt; a big flip clock with current weather, a monthly calendar and a D-Day counter&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Four clock styles&lt;/strong&gt; (Flip, Flip-Dashboard, Digital, Line), each in dark and light&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pomodoro timer:&lt;/strong&gt; 1 to 60 minutes with quick presets&lt;/li&gt;
&lt;li&gt;Show or hide seconds, date and battery; 12/24-hour format; optional tick sound; adjustable brightness&lt;/li&gt;
&lt;li&gt;Portrait and landscape layouts&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Design choices
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No ads, no account, no tracking.&lt;/strong&gt; The clock works fully offline.&lt;/li&gt;
&lt;li&gt;Weather is optional. If you turn it on, the app asks for your &lt;em&gt;approximate&lt;/em&gt; location and fetches the current weather from OpenWeather. Nothing else leaves the device.&lt;/li&gt;
&lt;li&gt;Settings stay hidden until you need them: swipe up for Settings, swipe left for the Pomodoro timer.&lt;/li&gt;
&lt;li&gt;It is plain Kotlin and XML, no extra SDKs.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;Google Play: &lt;a href="https://play.google.com/store/apps/details?id=com.withshy.flipclock" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.withshy.flipclock&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'd love honest feedback on what's missing or what feels off.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Weather data provided by OpenWeather.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>kotlin</category>
      <category>productivity</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
