<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ayda Nil Ozyurek on Medium]]></title>
        <description><![CDATA[Stories by Ayda Nil Ozyurek on Medium]]></description>
        <link>https://medium.com/@ozyurek.aydanil?source=rss-4629de7d7b61------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HPRk6iE4g66Ve2z0eXAPsw.jpeg</url>
            <title>Stories by Ayda Nil Ozyurek on Medium</title>
            <link>https://medium.com/@ozyurek.aydanil?source=rss-4629de7d7b61------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:59:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ozyurek.aydanil/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Theme Switching in HarmonyOS NEXT: Driving AttributeModifier, DrawModifier and GestureModifier from…]]></title>
            <link>https://medium.com/huawei-developers/theme-switching-in-harmonyos-next-driving-attributemodifier-drawmodifier-and-gesturemodifier-from-a95a0f2635a9?source=rss-4629de7d7b61------2</link>
            <guid isPermaLink="false">https://medium.com/p/a95a0f2635a9</guid>
            <category><![CDATA[state-management]]></category>
            <category><![CDATA[ark-ui]]></category>
            <category><![CDATA[ark-ts]]></category>
            <category><![CDATA[harmony-os]]></category>
            <category><![CDATA[wearables]]></category>
            <dc:creator><![CDATA[Ayda Nil Ozyurek]]></dc:creator>
            <pubDate>Mon, 24 Aug 2026 13:32:55 GMT</pubDate>
            <atom:updated>2026-08-24T13:32:55.951Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ulsh6djrRemfaDuhVYaPSw.png" /><figcaption>Theme switching with one state</figcaption></figure><h3>Theme Switching in HarmonyOS NEXT: Driving AttributeModifier, DrawModifier and GestureModifier from One State Source</h3><p><em>One State Management V2 update that restyles attributes, repaints custom drawing and keeps the gesture alive.</em></p><h3>Introduction</h3><p>Theme switching looks like a solved problem until you build it on a wearable. On a compact ArkUI screen a theme is rarely just a set of colors: it is component attributes, custom drawing behind and over a surface, and the interaction that triggers the switch in the first place.</p><p>ArkUI gives you a dedicated modifier for each of those concerns (AttributeModifier, DrawModifier, GestureModifier), but they do not follow the same reactivity rules. Wiring all three to the same variable and expecting them to update together is exactly where this breaks. This article shows a pattern that makes one theme switch restyle attributes, redraw decorations and keep the gesture working, all from a single observable source, and ends with a complete .ets component you can paste into an entry page and run.</p><h3>Problem / Requirement</h3><p>When the user switches themes, the whole UI should restyle at once. On a wearable this spans several kinds of styling: component attributes (colors, radius, fonts), custom drawing behind or over a surface, and interaction (a swipe that switches the theme).</p><p>Driving all of them from one piece of state does not make them update together, for three reasons:</p><ol><li>A custom AttributeModifier does not observe changes to captured state, so it will not restyle on its own.</li><li>A DrawModifier cannot be invoked inside attributeModifier, needs a UIContext for unit conversion, and redraws through its own invalidate().</li><li>A GestureModifier cannot attach to a custom component and cannot be called inside attributeModifier.</li></ol><p>The challenge is to combine all three under a single theme source so that one theme switch restyles attributes, redraws decorations, and keeps the gesture working at the same time.</p><h3>Technical Overview</h3><p><strong>One observable source of truth.</strong> With State Management V2, an @ObservedV2 holder exposes the active theme through a @Trace field. Any @ComponentV2 view that reads it rebuilds when it changes.</p><p><strong>Attribute modifier.</strong> Implements AttributeModifier&lt;T&gt;, setting attributes in applyNormalAttribute and pressed styling in applyPressedAttribute. Since it does not observe state, it must be rebuilt from the current theme on each render, not mutated.</p><p><strong>Draw modifier.</strong> Extends DrawModifier, overriding drawBehind / drawForeground and painting with drawing.Brush. It needs a UIContext (getUIContext()) to convert vp to px, is bound with .drawModifier(...), and each instance is set on one component only.</p><p><strong>Gesture modifier.</strong> Implements GestureModifier, adding gestures in applyGesture(event). It cannot attach to custom components, so it is bound to a plain container. It mutates the theme source.</p><p><strong>The unifying idea.</strong> Do not make each modifier reactive. Make one V2 view reactive, and rebuild the attribute and draw modifiers from the current theme on each render. The gesture mutates the @Trace field, that rebuilds the view, and the rebuild produces fresh modifiers carrying the new theme.</p><h3>Implementation</h3><h3>Step 1: One observable theme source</h3><p>An @ObservedV2 class holds the active theme index and cycles it:</p><pre>@ObservedV2<br>class ThemeState {<br>  @Trace index: number = 0;<br><br>cycle(): void {<br>    this.index = (this.index + 1) % 3;<br>  }<br>}</pre><h3>Step 2: Attribute modifier, rebuilt each render</h3><p>The button modifier is constructed inline from the current theme, so the rebuild carries the new values (including the pressed color):</p><pre>Button(&#39;Theme&#39;)<br>  .attributeModifier(new ThemedButtonModifier(this.engine.index))</pre><h3>Step 3: Draw modifier, one fresh instance per render</h3><p>The card’s decoration is a new DrawModifier built from the current theme and the UIContext. Each theme paints a distinct decoration, dots or stripes behind the content (drawBehind), or a frame over it (drawForeground), and it is bound with .drawModifier(...), not inside attributeModifier:</p><pre>Column()<br>  .drawModifier(new ThemedDrawModifier(this.getUIContext(), this.engine.index))</pre><h3>Step 4: Gesture modifier mutates the source</h3><p>A GestureModifier on a plain container turns a horizontal swipe into a theme cycle. It is the only thing that mutates the @Trace field:</p><pre>Column()<br>  .gestureModifier(this.swipeModifier) // calls state.cycle() on swipe</pre><p>One swipe flips the @Trace index, the view rebuilds, and Steps 2 and 3 produce fresh attribute and draw modifiers for the new theme. All three modifier types update from one swipe, even though only the attribute and draw modifiers are rebuilt.</p><h3>Code Example</h3><p>The complete, self-contained component is below. Paste it into an entry page and run it.</p><pre>// MultiModifierThemeDemo.ets<br>import { drawing } from &#39;@kit.ArkGraphics2D&#39;;<br><br>const WATCH_SIZE: string = &#39;466px&#39;;<br><br>// Three simple themes as plain data, selected by index.<br>enum DrawStyle { Dots, Stripes, Frame }<br><br>interface Theme {<br>  bg: ResourceColor;<br>  cardBg: ResourceColor;   // draw surface background - high contrast vs bg<br>  stripBg: ResourceColor;  // swipe strip background<br>  drawArgb: number;    // ARGB for the draw modifier decoration<br>  drawStyle: DrawStyle;<br>  buttonBg: ResourceColor;<br>  text: ResourceColor;<br>  pressed: ResourceColor;<br>  radius: number;<br>}<br><br>const THEMES: Theme[] = [<br>  // Light theme: cream background, white card, teal dots.<br>  { bg: &#39;#EFEAE0&#39;, cardBg: &#39;#FFFFFF&#39;, stripBg: &#39;#DCD4C4&#39;, drawArgb: 0xFF008C7A, drawStyle: DrawStyle.Dots,    buttonBg: &#39;#FFFFFF&#39;, text: &#39;#14181C&#39;, pressed: &#39;#00B39A&#39;, radius: 22 },<br>  // Dark theme: black background, bright orange card, dark stripes.<br>  { bg: &#39;#050505&#39;, cardBg: &#39;#FF4D1C&#39;, stripBg: &#39;#2A2A2A&#39;, drawArgb: 0x66000000, drawStyle: DrawStyle.Stripes, buttonBg: &#39;#FF4D1C&#39;, text: &#39;#FFFFFF&#39;, pressed: &#39;#FF7043&#39;, radius: 8 },<br>  // Gold theme: navy background, gold card, navy frame.<br>  { bg: &#39;#0B0E14&#39;, cardBg: &#39;#D4AF37&#39;, stripBg: &#39;#1B2436&#39;, drawArgb: 0xFF0B0E14, drawStyle: DrawStyle.Frame,   buttonBg: &#39;#D4AF37&#39;, text: &#39;#FFFFFF&#39;, pressed: &#39;#E5C55A&#39;, radius: 4 }<br>];<br><br>// Single observable source of truth.<br>@ObservedV2<br>class ThemeEngine {<br>  @Trace index: number = 0;<br><br>  cycle(): void {<br>    this.index = (this.index + 1) % THEMES.length;<br>  }<br>}<br><br>// Attribute modifier: rebuilt each render from the current theme.<br>class ThemedButtonModifier implements AttributeModifier&lt;ButtonAttribute&gt; {<br>  private theme: Theme;<br><br>  constructor(index: number) {<br>    this.theme = THEMES[index];<br>  }<br><br>  applyNormalAttribute(instance: ButtonAttribute): void {<br>    instance.backgroundColor(this.theme.buttonBg);<br>    instance.fontColor(this.theme.text);<br>    instance.borderRadius(this.theme.radius);<br>  }<br><br>  applyPressedAttribute(instance: ButtonAttribute): void {<br>    instance.backgroundColor(this.theme.pressed);<br>  }<br>}<br><br>// Draw modifier: one fresh instance per render. Each theme draws a distinct<br>// decoration - dots, stripes, or a frame with drawing.Brush.<br>class ThemedDrawModifier extends DrawModifier {<br>  private uiContext: UIContext;<br>  private argb: number;<br>  private style: DrawStyle;<br><br>  constructor(uiContext: UIContext, index: number) {<br>    super();<br>    this.uiContext = uiContext;<br>    this.argb = THEMES[index].drawArgb;<br>    this.style = THEMES[index].drawStyle;<br>  }<br><br>  private brush(): drawing.Brush {<br>    const b = new drawing.Brush();<br>    b.setColor({<br>      alpha: (this.argb &gt;&gt;&gt; 24) &amp; 0xFF,<br>      red: (this.argb &gt;&gt;&gt; 16) &amp; 0xFF,<br>      green: (this.argb &gt;&gt;&gt; 8) &amp; 0xFF,<br>      blue: this.argb &amp; 0xFF<br>    });<br>    return b;<br>  }<br><br>  // Dots and Stripes are painted behind the card content.<br>  drawBehind(context: DrawContext): void {<br>    const w = context.size.width;<br>    const h = context.size.height;<br><br>    if (this.style === DrawStyle.Dots) {<br>      context.canvas.attachBrush(this.brush());<br>      const gap = 20;<br>      const r = 4;<br>      for (let y = gap; y &lt; h; y += gap) {<br>        for (let x = gap; x &lt; w; x += gap) {<br>          context.canvas.drawCircle(<br>            this.uiContext.vp2px(x),<br>            this.uiContext.vp2px(y),<br>            this.uiContext.vp2px(r)<br>          );<br>        }<br>      }<br>      context.canvas.detachBrush();<br>    } else if (this.style === DrawStyle.Stripes) {<br>      context.canvas.attachBrush(this.brush());<br>      const step = 20;<br>      for (let x = 0; x &lt; w; x += step) {<br>        context.canvas.drawRect({<br>          left: this.uiContext.vp2px(x),<br>          top: this.uiContext.vp2px(0),<br>          right: this.uiContext.vp2px(x + 7),<br>          bottom: this.uiContext.vp2px(h)<br>        });<br>      }<br>      context.canvas.detachBrush();<br>    }<br>  }<br><br>  // Frame is painted over the card content (four edge rects).<br>  drawForeground(context: DrawContext): void {<br>    if (this.style !== DrawStyle.Frame) {<br>      return;<br>    }<br>    context.canvas.attachBrush(this.brush());<br>    const w = context.size.width;<br>    const h = context.size.height;<br>    const t = 3;<br>    context.canvas.drawRect({<br>      left: this.uiContext.vp2px(0), top: this.uiContext.vp2px(0),<br>      right: this.uiContext.vp2px(w), bottom: this.uiContext.vp2px(t)<br>    });<br>    context.canvas.drawRect({<br>      left: this.uiContext.vp2px(0), top: this.uiContext.vp2px(h - t),<br>      right: this.uiContext.vp2px(w), bottom: this.uiContext.vp2px(h)<br>    });<br>    context.canvas.drawRect({<br>      left: this.uiContext.vp2px(0), top: this.uiContext.vp2px(0),<br>      right: this.uiContext.vp2px(t), bottom: this.uiContext.vp2px(h)<br>    });<br>    context.canvas.drawRect({<br>      left: this.uiContext.vp2px(w - t), top: this.uiContext.vp2px(0),<br>      right: this.uiContext.vp2px(w), bottom: this.uiContext.vp2px(h)<br>    });<br>    context.canvas.detachBrush();<br>  }<br>}<br><br>// Gesture modifier: horizontal swipe cycles the theme. Stable instance.<br>class SwipeModifier implements GestureModifier {<br>  private onSwipe: () =&gt; void;<br><br>  constructor(onSwipe: () =&gt; void) {<br>    this.onSwipe = onSwipe;<br>  }<br><br>  applyGesture(event: UIGestureEvent): void {<br>    event.addGesture(<br>      new PanGestureHandler({ direction: PanDirection.Horizontal })<br>        .onActionEnd(() =&gt; {<br>          this.onSwipe();<br>        })<br>    );<br>  }<br>}<br><br>@Entry<br>@ComponentV2<br>struct MultiModifierThemeDemo {<br>  private engine: ThemeEngine = new ThemeEngine();<br>  private swipeModifier: SwipeModifier = new SwipeModifier(() =&gt; {<br>    this.engine.cycle();<br>  });<br><br>  build() {<br>    Column({ space: 18 }) {<br>      // Attribute modifier: rebuilt each render.<br>      Button(&#39;Theme&#39;)<br>        .attributeModifier(new ThemedButtonModifier(this.engine.index))<br>        .width(&#39;50%&#39;)<br>        .height(44)<br><br>      // Draw modifier: fresh instance each render, bound via drawModifier.<br>      Column()<br>        .width(&#39;50%&#39;)<br>        .height(52)<br>        .backgroundColor(THEMES[this.engine.index].cardBg)<br>        .borderRadius(THEMES[this.engine.index].radius)<br>        .drawModifier(new ThemedDrawModifier(this.getUIContext(), this.engine.index))<br><br>      // Gesture modifier: swipe strip that drives the theme source.<br>      Column() {<br>        Text(&#39;Swipe to\nchange theme&#39;)<br>          .fontSize(13)<br>          .maxLines(2)<br>          .fontColor(THEMES[this.engine.index].text)<br>          .textAlign(TextAlign.Center)<br>          .width(&#39;100%&#39;)<br>      }<br>      .width(&#39;62%&#39;)<br>      .height(56)<br>      .justifyContent(FlexAlign.Center)<br>      .backgroundColor(THEMES[this.engine.index].stripBg)<br>      .borderRadius(THEMES[this.engine.index].radius)<br>      .gestureModifier(this.swipeModifier)<br>    }<br>    .width(WATCH_SIZE)<br>    .height(WATCH_SIZE)<br>    .justifyContent(FlexAlign.Center)<br>    .backgroundColor(THEMES[this.engine.index].bg)<br>  }<br>}</pre><h3>Explanation</h3><p>The update path is deliberately linear. The swipe lands on the plain Column carrying SwipeModifier, whose applyGesture registered a horizontal PanGestureHandler. Its onActionEnd calls ThemeEngine.cycle(), which mutates index, a @Trace field on an @ObservedV2 class.</p><p>Because MultiModifierThemeDemo is a @ComponentV2 view that reads this.engine.index, that mutation invalidates the view and build() runs again. On that pass:</p><ul><li>new ThemedButtonModifier(this.engine.index) is evaluated again, so the button receives a modifier whose captured Theme is the new one, including the applyPressedAttribute color that would otherwise stay stale.</li><li>new ThemedDrawModifier(this.getUIContext(), this.engine.index) is evaluated again, so the card gets the new ARGB value and the new DrawStyle, and the canvas is repainted with a different decoration.</li><li>this.swipeModifier is not rebuilt. It is a field, created once, and it carries no theme data.</li></ul><p>That is why the pattern holds together: reactivity lives in exactly one place, and the modifiers are treated as disposable values derived from the current theme rather than as long-lived reactive objects.</p><p>Two details inside the draw modifier are worth noting. context.size is reported in vp while the canvas draws in px, which is why every coordinate passes through uiContext.vp2px(...). And the ARGB constant is unpacked with unsigned right shifts before reaching drawing.Brush.setColor, which expects separate alpha, red, green and blue channels.</p><h3>Testing / Results</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*gHxkSGR2_B9xqRQeXRzQfw.gif" /><figcaption><em>One horizontal swipe cycles Light, Dark and Gold. The button attributes, the painted decoration and the corner radius all change in the same rebuild.</em></figcaption></figure><p>Running the component on a wearable device or emulator gives three states:</p><ol><li><strong>Light</strong>: cream background, white card, teal dots painted behind the card via drawBehind, 22 vp radius.</li><li><strong>Dark</strong>: black background, orange card, translucent dark stripes behind the card, 8 vp radius.</li><li><strong>Gold</strong>: navy background, gold card, navy frame painted over the card via drawForeground, 4 vp radius.</li></ol><p>Three checks confirm the pattern is working:</p><ul><li>A single swipe changes the background, button, card and decoration together, with no partial update.</li><li>Pressing and holding the button shows the theme specific pressed color, confirming applyPressedAttribute was refreshed rather than left on the previous theme.</li><li>The swipe still works after several theme changes, confirming the stable GestureModifier instance is unaffected by the rebuilds.</li></ul><h3>Limitations and Considerations</h3><ul><li><strong>State Management V2 is required.</strong> The pattern depends on @ObservedV2, @Trace and @ComponentV2. Under V1 nothing rebuilds and none of the modifiers refresh.</li><li><strong>Attribute modifiers do not observe state.</strong> Rebuild them each render, never mutate an existing instance and expect the UI to follow.</li><li><strong>Draw modifier instances are per component.</strong> Each instance is set on one component only, so sharing one instance across several components is not a valid shortcut.</li><li><strong>Gesture modifiers cannot attach to custom components.</strong> The swipe target has to be a built-in container.</li><li><strong>Allocation per render.</strong> New modifier objects are created on every rebuild. That is intentional and cheap at this scale, but worth keeping in mind if the approach is applied to a long list where rebuilds are frequent.</li></ul><h3>Conclusion</h3><p>Modifier types in ArkUI have different reactivity rules, and fighting each of them separately leads to a fragile design. The simpler path is to centralize the theme in a State Management V2 observable, let the gesture be the only thing that mutates it, and rebuild the attribute and draw modifiers from the current theme on each render.</p><p>One state change then restyles attributes, redraws decorations and keeps interaction working, through a single update path that is easy to reason about and easy to extend with a fourth theme or a new themed component.</p><h3>References</h3><ul><li>HarmonyOS NEXT documentation: <a href="https://developer.huawei.com/consumer/en/doc/harmonyos-references/ts-universal-attributes-attribute-modifier#attributemodifier">Attribute Modifier</a></li><li>HarmonyOS NEXT documentation: <a href="https://developer.huawei.com/consumer/en/doc/harmonyos-references/ts-universal-attributes-draw-modifier">Drawing Modifier</a> (DrawModifier)</li><li>HarmonyOS NEXT documentation: <a href="https://developer.huawei.com/consumer/en/doc/harmonyos-references/ts-universal-attributes-gesture-modifier">Gesture Modifier</a></li><li>HarmonyOS NEXT documentation: <a href="https://developer.huawei.com/consumer/en/doc/harmonyos-guides/arkts-new-observedv2-and-trace">State Management V2</a> (@ObservedV2, @Trace, @ComponentV2)</li><li>HarmonyOS NEXT documentation: <a href="https://developer.huawei.com/consumer/en/doc/harmonyos-references/arkts-apis-graphics-drawing-brush">ArkGraphics 2D</a> (@kit.ArkGraphics2D, drawing.Brush)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a95a0f2635a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/huawei-developers/theme-switching-in-harmonyos-next-driving-attributemodifier-drawmodifier-and-gesturemodifier-from-a95a0f2635a9">Theme Switching in HarmonyOS NEXT: Driving AttributeModifier, DrawModifier and GestureModifier from…</a> was originally published in <a href="https://medium.com/huawei-developers">Huawei Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Get a TMDB API Key (Even If Your Project Doesn’t Exist Yet)]]></title>
            <link>https://medium.com/@ozyurek.aydanil/how-to-get-a-tmdb-api-key-even-if-your-project-doesnt-exist-yet-fae8845f00c6?source=rss-4629de7d7b61------2</link>
            <guid isPermaLink="false">https://medium.com/p/fae8845f00c6</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[tmdb]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[tutorial]]></category>
            <dc:creator><![CDATA[Ayda Nil Ozyurek]]></dc:creator>
            <pubDate>Sat, 18 Apr 2026 12:08:45 GMT</pubDate>
            <atom:updated>2026-04-18T12:08:45.196Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EhtiybrYqQcTlBSNY61nmw.jpeg" /></figure><p>A practical walkthrough for developers building their first movie app — even if your project is just an idea right now.</p><p>I was building a Flutter movie app for my portfolio when I hit the TMDB registration form. It asked for an “Application URL” and I didn’t have one yet. No deployed site, no GitHub repo, just an idea.</p><p>If you’re in the same spot, here’s what to do.</p><h3>1. Sign up at <a href="https://www.themoviedb.org/">themoviedb.org</a></h3><p>Standard signup, verify your email. Takes two minutes.</p><h3>2. Request the API key</h3><p>Go to <strong>Settings → API → Request an API Key</strong> and pick the <strong>Developer</strong> plan. It’s free forever.</p><h3>3. Fill the form</h3><p>This is where people get stuck. Here’s what to put in the tricky fields:</p><ul><li><strong>Application Name:</strong> Whatever you plan to call your project. Not final.</li><li><strong>Application URL:</strong> No live project? Use your GitHub profile, an empty repo, or https://localhost. TMDB accepts all of these.</li><li><strong>Type of Use:</strong> Mobile Application, Website, or whatever fits.</li><li><strong>Application Summary:</strong> Be honest. I wrote: <em>“A personal learning project — a Flutter movie discovery app for educational and portfolio purposes only.”</em></li></ul><p>The phrase “educational and portfolio purposes only” helps with approval. You’re being upfront, which is what they want.</p><p>Fill in your real contact info (nobody calls you, it’s just for their records), accept the terms, submit.</p><p>Approval is often <em>instant</em>. Worst case, a few hours.</p><h3>4. You’ll get two tokens — use the right one</h3><p>TMDB gives you both an <strong>API Key (v3)</strong> and a <strong>Read Access Token (v4)</strong>. Their docs don’t make this clear:</p><ul><li><strong>v3</strong> passes the key in the URL: ?api_key=xxx</li><li><strong>v4</strong> passes it as a Bearer token in the header: Authorization: Bearer xxx</li></ul><p><strong>Use v4.</strong> It’s the modern standard, more secure, and what every new project should use.</p><h3>5. Test it before you code</h3><p>Run this in your terminal (replace YOUR_TOKEN):</p><pre>curl --request GET \<br>  --url &#39;https://api.themoviedb.org/3/movie/popular&#39; \<br>  --header &#39;Authorization: Bearer YOUR_TOKEN&#39;</pre><p>If you get back a JSON list of movies, you’re done. If not, double-check the token.</p><p>No terminal? Use <a href="https://www.postman.com/">Postman</a> — same request, nicer UI.</p><h3>A couple of safety notes</h3><p>Don’t commit your token to Git — use a .env file. For production mobile apps, you&#39;ll want to proxy requests through your own backend, because tokens bundled into apps can be extracted. For portfolio projects, a .env is enough.</p><p>That’s it. The form looks scarier than it is. If this helped, a clap would be nice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fae8845f00c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9 Errors I Fixed While Releasing My First Flutter iOS App to TestFlight]]></title>
            <link>https://medium.com/@ozyurek.aydanil/9-errors-i-fixed-while-releasing-my-first-flutter-ios-app-to-testflight-516c23493b19?source=rss-4629de7d7b61------2</link>
            <guid isPermaLink="false">https://medium.com/p/516c23493b19</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile-development]]></category>
            <category><![CDATA[testflight]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[firebase]]></category>
            <dc:creator><![CDATA[Ayda Nil Ozyurek]]></dc:creator>
            <pubDate>Sat, 28 Mar 2026 14:29:40 GMT</pubDate>
            <atom:updated>2026-04-20T19:55:11.544Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QdsqJbtQawxYzzqQiLwe-g.png" /></figure><p><em>A no-fluff guide to Apple Developer setup, Xcode signing, Firebase, and CocoaPods — from someone who hit every wall.</em></p><p>I thought publishing my first Flutter app to TestFlight would be the easy part.</p><p><em>I was wrong.</em></p><p>After weeks of building the app itself, I spent two full days fighting Apple Developer enrollment, Xcode signing errors, Firebase mismatches, and CocoaPods sync issues — none of which had anything to do with my actual code.</p><p>This is the article I wish I had found before I started. Below are all 9 errors I hit, in the exact order they happened, with the fix for each one.</p><h3>1. Apple Developer Program — Team Not Showing in Xcode</h3><p><strong>Before anything else, you need to enroll in the Apple Developer Program.</strong></p><ul><li>Cost: $99/year (Apple charged me the equivalent of 1,029 TRY)</li><li>Approval usually takes a few hours after payment</li></ul><p>After my account was approved, Xcode still showed</p><pre>Personal Team</pre><p>instead of my actual developer team.</p><h4>Why this happens</h4><p>Xcode caches your account state. It doesn’t automatically detect that Apple just upgraded your membership.</p><p>✅<strong> Fix: </strong>Sign out and sign back into your Apple ID in <strong><em>Xcode → Settings → Accounts</em></strong>. Your developer team will appear after re-login.</p><pre>Xcode → Settings → Accounts</pre><h3>2. Bundle Identifier Already Taken</h3><p><strong>When creating the App ID in the Apple Developer portal, I tried the obvious:</strong></p><pre>com.example.app</pre><p>❌<strong> Error: </strong>The app identifier cannot be registered to your development team because it is not available.</p><h3>Why this happens</h3><p>Bundle identifiers are globally unique across every Apple developer. Someone already claimed that one.</p><p>✅<strong> Fix: </strong>Use a reverse-domain format with your own name or domain:</p><pre>com.yourdomain.exampleapp</pre><p><strong>Register it under</strong>:</p><pre>Certificates, Identifiers &amp; Profiles → Identifiers</pre><h3>3. Xcode Signing Error: No Provisioning Profile Found</h3><p>❌<strong> Error: </strong>No profiles for ‘com.example.app’ were found</p><p>— or —</p><p>Your team has no devices from which to generate a provisioning profile</p><h4>Why this happens</h4><p>Apple cannot generate a development provisioning profile unless <strong>at least one device is registered to your developer account</strong>.</p><p><strong>✅ Fix: </strong>Connect an iPhone to your Mac and run the project once.</p><p>Steps:</p><ol><li>Plug the iPhone into the Mac</li><li>Select the device in Xcode</li><li>Run the project</li></ol><p>Xcode automatically:</p><ul><li>registers the device</li><li>generates the provisioning profile</li><li>creates the signing certificate</li></ul><p>After this step, the signing issue disappeared.</p><h3>4. macOS Keychain Popup: codesign Wants Access</h3><p>Mid-build, macOS interrupted with a popup:</p><pre>codesign wants to access key &quot;Apple Development&quot;</pre><h4>Why this happens</h4><p>Xcode needs access to the signing certificate stored in your macOS Keychain. It asks for permission the first time.</p><p>✅<strong> Fix: </strong>Enter your <strong>Mac login password</strong> and click Always Allow. This prevents the popup from appearing on every future build.</p><h3>5. CocoaPods Sandbox Not in Sync</h3><p>Another issue appeared during the build process:</p><pre>The sandbox is not in sync with the Podfile.lock<br>Run &#39;pod install&#39;</pre><h4>Why this happens</h4><p>The CocoaPods dependency cache is out of sync — common after running flutter clean or switching branches.</p><p>✅ <strong>Fix</strong>: Run the following commands:</p><pre>flutter clean<br>flutter pub get<br>cd ios<br>pod install<br>cd ..</pre><p>Then rebuild the project.</p><h3>6. Firebase Stopped Working After Changing Bundle ID</h3><p>After fixing my bundle identifier, Firebase completely stopped working in the app.</p><h4>Why this happens</h4><p>Firebase apps are tied to a specific bundle identifier. Change the bundle ID and Firebase no longer recognizes your app.</p><p>✅ <strong>Fix: </strong>Add a new iOS app inside Firebase with the correct bundle ID.</p><p>Steps:</p><ol><li>Open Firebase Console</li><li>Add a new iOS app</li><li>Use the updated bundle identifier</li><li>Download the new configuration file</li></ol><pre>GoogleService-Info.plist</pre><p>Replace the old file inside:</p><pre>ios/Runner</pre><p>Then regenerate Firebase configuration:</p><pre>flutterfire configure</pre><p>When prompted:</p><pre>Generated firebase_options.dart already exists<br>Override?</pre><p>Choose:</p><pre>Yes</pre><p>Otherwise, the old configuration will remain.</p><h3>7. App Name Already Taken in App Store Connect</h3><p>While creating the app in App Store Connect, I encountered this message:</p><pre>The app name you entered is already being used</pre><h4>Why this happens</h4><p>App names must be globally unique across the entire App Store, just like bundle identifiers.</p><p>✅<strong> Fix: </strong>Add a descriptive suffix to differentiate your app name. Examples: ‘Example App — AI Generator’ or ‘Example AI Photo App’.</p><h3>8. Setting Up the App in App Store Connect</h3><p>Once your name is available, create the app entry:</p><p><strong>1. Open App Store Connect → Apps → Add App</strong></p><p><strong>2. Set Name, Primary Language, Bundle ID, and SKU</strong></p><p><strong>3. Save — the app record is now created</strong></p><h3>9. Archiving and Uploading to TestFlight</h3><p>With everything configured, the final step is creating the archive in Xcode:</p><p>1. Product → Archive</p><p>2. Once the archive completes: Distribute App → App Store Connect → Upload</p><p>3. Wait 10–30 minutes for processing</p><p>After processing, the build appears under App Store Connect → TestFlight and you can invite testers.</p><h3>Final Thoughts</h3><p>Nearly every error I hit was infrastructure, not code. The actual Flutter app was fine — it was Apple’s signing system, Firebase configuration, and CocoaPods that needed attention.</p><p>The good news: once you’ve done this once, future releases are dramatically smoother. These are one-time setup pains, not recurring ones.</p><p>If you’re preparing your first Flutter iOS release, I hope this guide saves you the two days it cost me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=516c23493b19" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting Up Firebase in a Flutter App on macOS (Real Errors & Fixes)]]></title>
            <link>https://medium.com/@ozyurek.aydanil/setting-up-firebase-in-a-flutter-app-on-macos-real-errors-fixes-f54547716bc3?source=rss-4629de7d7b61------2</link>
            <guid isPermaLink="false">https://medium.com/p/f54547716bc3</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[flutter-tips]]></category>
            <category><![CDATA[firebase]]></category>
            <dc:creator><![CDATA[Ayda Nil Ozyurek]]></dc:creator>
            <pubDate>Mon, 09 Feb 2026 17:03:32 GMT</pubDate>
            <atom:updated>2026-02-09T17:03:32.672Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zTImi5zfoeg4RlG7DmjLdg.png" /></figure><p>If you’re integrating Firebase into a Flutter project on macOS and you want a simple, reliable checklist, this is the exact path I followed while setting up Firebase for my app.</p><p>This is intentionally practical: I’m including the real issues I encountered (and how I fixed them), because those are usually what slows you down.</p><h4>What You’ll End Up With</h4><p>By the end, you’ll have:</p><ul><li>A Firebase project connected to your Flutter app</li><li>firebase_options.dart generated and ready</li><li>iOS + Android registered</li><li>The app running successfully on an iOS simulator</li><li>A clean fix for the <strong>iOS deployment target</strong> Firebase requires</li></ul><h3>Step 1 — Create a Firebase Project</h3><p>Go to Firebase Console and create a new project.<br> You don’t need to enable every feature yet—just create the project.</p><h3>Step 2 — Install Firebase CLI (Fix: “firebase: command not found”)</h3><p>My first command was:</p><pre>firebase login</pre><p>…and I got:</p><p>zsh: command not found: firebase</p><p>That means the <strong>Firebase CLI</strong> isn’t installed. On macOS, the easiest way is Homebrew:</p><pre>brew install firebase-cli</pre><p>Then verify:</p><pre>firebase --version</pre><p>Now login works:</p><pre>firebase login</pre><h3>Step 3 — Install FlutterFire CLI (Fix: “flutterfire not found”)</h3><p>Firebase CLI is not the same as FlutterFire CLI. FlutterFire is the tool that generates Flutter platform config and firebase_options.dart.</p><p>Install it:</p><pre>dart pub global activate flutterfire_cli</pre><p>If your terminal can’t find flutterfire, add pub cache to PATH:</p><pre>export PATH=&quot;$PATH&quot;:&quot;$HOME/.pub-cache/bin&quot;</pre><p>To make it permanent (so you don’t repeat this every time):</p><pre>echo &#39;export PATH=&quot;$PATH&quot;:&quot;$HOME/.pub-cache/bin&quot;&#39; &gt;&gt; ~/.zshrc<br>source ~/.zshrc</pre><p>Check:</p><pre>flutterfire --version</pre><h3>Step 4 — Configure Firebase for Your Flutter App</h3><p>In your Flutter project root:</p><pre>flutterfire configure</pre><p>During setup:</p><ul><li>Select your Firebase project</li><li>Select <strong>android</strong> and <strong>ios</strong></li><li>Let the CLI register apps and generate config</li></ul><p>After this, you should have:</p><ul><li>lib/firebase_options.dart</li><li>Android config (google-services.json)</li><li>iOS config (GoogleService-Info.plist)</li></ul><h3>Step 5 — Add Firebase Core + Initialize Firebase in main.dart</h3><p>Add the dependency:</p><pre>flutter pub add firebase_core</pre><p>Then initialize Firebase before running the app:</p><pre>import &#39;package:firebase_core/firebase_core.dart&#39;;<br>import &#39;firebase_options.dart&#39;;</pre><pre>Future&lt;void&gt; main() async {<br>  WidgetsFlutterBinding.ensureInitialized();</pre><pre>  await Firebase.initializeApp(<br>    options: DefaultFirebaseOptions.currentPlatform,<br>  );</pre><pre>  runApp(const App());<br>}</pre><p>If you also use dependency injection, initialize Firebase <strong>before</strong> initDependencies().</p><h3>Step 6 — Fix iOS Build Error: “requires a higher minimum iOS deployment version”</h3><p>When I tried to run on iOS, I hit:</p><blockquote><em>The plugin “firebase_core” requires a higher minimum iOS deployment version…<br> increase deployment target to at least 15.0</em></blockquote><p>So I updated the iOS deployment target to <strong>15.0</strong>.</p><h4>Update ios/Podfile</h4><p>My Podfile had the platform line commented out (or set lower). I changed it to:</p><pre>platform :ios, &#39;15.0&#39;</pre><p>Then I forced all pods to use 15.0 inside post_install:</p><pre>post_install do |installer|<br>  installer.pods_project.targets.each do |target|<br>    flutter_additional_ios_build_settings(target)</pre><pre>    target.build_configurations.each do |config|<br>      config.build_settings[&#39;IPHONEOS_DEPLOYMENT_TARGET&#39;] = &#39;15.0&#39;<br>    end<br>  end<br>end</pre><h4>Clean &amp; reinstall pods</h4><p>From the project root:</p><pre>flutter clean<br>rm -rf ios/Pods ios/Podfile.lock<br>flutter pub get<br>cd ios<br>pod install<br>cd ..</pre><h3>Step 7 — Fix “No Podfile found” (Wrong directory)</h3><p>At one point I ran:</p><pre>pod install</pre><p>and got:</p><blockquote><em>No </em><em>Podfile found in the project directory.</em></blockquote><p>That was simply because I ran it in the <strong>project root</strong>, not inside ios/.</p><p>Correct command:</p><pre>cd ios<br>pod install<br>cd ..</pre><p>This was my complete Firebase setup process for a Flutter app on macOS, including the real errors I ran into and how I fixed them.<br> Hopefully, this saves you some time when setting things up in your own project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f54547716bc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Clean & Productive VS Code Setup for Flutter & Dart Developers]]></title>
            <link>https://medium.com/@ozyurek.aydanil/a-clean-productive-vs-code-setup-for-flutter-dart-developers-6fba37f050bc?source=rss-4629de7d7b61------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fba37f050bc</guid>
            <category><![CDATA[mobile-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[developer-productivity]]></category>
            <category><![CDATA[dart]]></category>
            <dc:creator><![CDATA[Ayda Nil Ozyurek]]></dc:creator>
            <pubDate>Thu, 05 Feb 2026 09:31:00 GMT</pubDate>
            <atom:updated>2026-04-20T19:52:04.185Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L7Je-ipwmNrs0UwieWrQlw.png" /></figure><p>When you work with Flutter and Dart daily, your editor configuration directly affects your focus, speed, and code quality.</p><p>After researching VS Code documentation, Dart-Code recommendations, and real Flutter workflows, I put together a settings.json that is <strong>especially well-suited for Flutter/Dart developers</strong> — clean, predictable, and productivity-oriented.</p><p>Instead of overloading VS Code with aggressive automation, this setup focuses on <strong>clarity and control</strong>.</p><p>Below, I’ll walk through each group of settings briefly.</p><h3>Formatting: Let Dart Handle It</h3><p>Flutter code depends heavily on clean structure and readable widget trees.<br>Automatic formatting removes friction and keeps code consistent across files.</p><pre>&quot;editor.formatOnSave&quot;: true,<br>&quot;editor.formatOnType&quot;: true,<br>&quot;editor.formatOnPaste&quot;: true</pre><p>To ensure consistency with dart format, the Dart-Code formatter is explicitly set for Dart files:</p><pre>&quot;[dart]&quot;: {<br>  &quot;editor.defaultFormatter&quot;: &quot;Dart-Code.dart-code&quot;,<br>  &quot;editor.formatOnSave&quot;: true<br>}</pre><p>This guarantees that local formatting, CI, and team conventions stay aligned.</p><h3>Save Actions: Clean Imports Without Risky Fixes</h3><p>Organizing imports on every save keeps files tidy as projects grow:</p><pre>&quot;editor.codeActionsOnSave&quot;: {<br>  &quot;source.organizeImports&quot;: &quot;always&quot;,<br>  &quot;source.fixAll&quot;: &quot;explicit&quot;<br>}</pre><p>The important detail here is fixAll: explicit</p><p>With autosave enabled, this prevents large or potentially risky fixes from running automatically.<br>Fixes are applied only when you explicitly save — a safer and more professional workflow for Flutter projects.</p><h3>Flutter &amp; Dart Quality-of-Life Features</h3><p>These small settings have a big impact when working with widget-heavy files:</p><pre>&quot;dart.previewFlutterUiGuides&quot;: true,<br>&quot;dart.closingLabels&quot;: true,<br>&quot;dart.showTodos&quot;: true</pre><p>They help visualize widget boundaries, keep nested layouts readable, and surface TODOs without external tooling.</p><h3>Line Length: Structure Over Wrapping</h3><p>Dart formatting revolves around a single concept: <strong>line length</strong>.</p><pre>&quot;dart.lineLength&quot;: 100,<br>&quot;editor.rulers&quot;: [80, 100],<br>&quot;editor.wordWrap&quot;: &quot;off&quot;</pre><ul><li>80 characters acts as a soft guide</li><li>100 characters is the hard limit enforced by the formatter</li></ul><p>Word wrap is disabled intentionally — explicit line breaks are far easier to reason about in Flutter widget trees.</p><h3>Editor Readability for Large Widget Trees</h3><p>Flutter files grow fast. These settings reduce visual noise and improve orientation:</p><pre>&quot;editor.bracketPairColorization.enabled&quot;: true,<br>&quot;editor.guides.bracketPairs&quot;: true,<br>&quot;editor.guides.indentation&quot;: true,<br>&quot;editor.inlineSuggest.enabled&quot;: true,<br>&quot;editor.stickyScroll.enabled&quot;: true,<br>&quot;workbench.editor.highlightModifiedTabs&quot;: true</pre><p>They make deeply nested layouts easier to scan and understand at a glance.</p><h3>JSON &amp; YAML Formatting (Flutter Config Files)</h3><p>Flutter projects rely heavily on configuration files such as:</p><ul><li>pubspec.yaml</li><li>analysis_options.yaml</li><li>Firebase and build configs</li></ul><p>Explicit formatting ensures these files stay clean and consistent:</p><pre>&quot;[json]&quot;: {<br>  &quot;editor.formatOnSave&quot;: true<br>},<br>&quot;[yaml]&quot;: {<br>  &quot;editor.formatOnSave&quot;: true<br>}</pre><p>This does <strong>not</strong> affect Dart formatting and keeps configs readable without manual effort.</p><h3>Window, Debug &amp; Autosave Behavior</h3><p>A small UI improvement that keeps the editor focused:</p><pre>&quot;window.commandCenter&quot;: true,<br>&quot;debug.toolBarLocation&quot;: &quot;commandCenter&quot;</pre><p>Autosave is enabled for fast iteration:</p><pre>&quot;files.autoSave&quot;: &quot;afterDelay&quot;</pre><p>Combined with explicit fix-all behavior, this setup works smoothly with hot reload and frequent edits.</p><h3>Full Version — settings.json</h3><p>Here is the complete configuration used in this setup:</p><pre>{<br>  // ============================================================<br>  // Flutter/Dart — Productivity Settings<br>  // ============================================================<br><br>  // -------------------------<br>  // Formatting (Dart Formatter)<br>  // -------------------------<br>  &quot;editor.formatOnSave&quot;: true,<br>  &quot;editor.formatOnType&quot;: true,<br>  &quot;editor.formatOnPaste&quot;: true,<br><br>  // Use Dart-Code formatter for Dart files<br>  &quot;[dart]&quot;: {<br>    &quot;editor.defaultFormatter&quot;: &quot;Dart-Code.dart-code&quot;,<br>    &quot;editor.formatOnSave&quot;: true<br>  },<br><br>  // -----------------------------------------<br>  // Save Actions (Imports / Quick Fixes)<br>  // -----------------------------------------<br>  &quot;editor.codeActionsOnSave&quot;: {<br>    &quot;source.organizeImports&quot;: &quot;always&quot;,<br>    &quot;source.fixAll&quot;: &quot;explicit&quot;<br>  },<br><br>  // -----------------------------------------<br>  // Dart/Flutter Extension Quality-of-Life<br>  // -----------------------------------------<br>  &quot;dart.previewFlutterUiGuides&quot;: true,<br>  &quot;dart.closingLabels&quot;: true,<br>  &quot;dart.showTodos&quot;: true,<br><br>  // -----------------------------------------<br>  // Line Length &amp; Visual Guides<br>  // -----------------------------------------<br>  &quot;dart.lineLength&quot;: 100,<br>  &quot;editor.rulers&quot;: [80, 100],<br>  &quot;editor.wordWrap&quot;: &quot;off&quot;,<br><br>  // -----------------------------------------<br>  // Editor Readability (great for widget trees)<br>  // -----------------------------------------<br>  &quot;editor.bracketPairColorization.enabled&quot;: true,<br>  &quot;editor.guides.bracketPairs&quot;: true,<br>  &quot;editor.guides.indentation&quot;: true,<br>  &quot;editor.inlineSuggest.enabled&quot;: true,<br>  &quot;editor.stickyScroll.enabled&quot;: true,<br>  &quot;workbench.editor.highlightModifiedTabs&quot;: true,<br><br>  // -----------------------------------------<br>  // JSON / YAML Formatting (Flutter configs)<br>  // -----------------------------------------<br>  &quot;[json]&quot;: {<br>    &quot;editor.formatOnSave&quot;: true<br>  },<br>  &quot;[yaml]&quot;: {<br>    &quot;editor.formatOnSave&quot;: true<br>  },<br><br>  // -----------------------------------------<br>  // Window / Debug UI<br>  // -----------------------------------------<br>  &quot;window.commandCenter&quot;: true,<br>  &quot;debug.toolBarLocation&quot;: &quot;commandCenter&quot;,<br><br>  // -----------------------------------------<br>  // Auto Save<br>  // -----------------------------------------<br>  &quot;files.autoSave&quot;: &quot;afterDelay&quot;<br>}</pre><h4>Use This Setup in Your Own Workflow</h4><p>If you want to use this configuration directly or keep it updated, you can find the full setup on GitHub:<br><a href="https://github.com/aydozy/flutter-vscode-settings">https://github.com/aydozy/flutter-vscode-settings</a></p><h3>Final Thoughts</h3><p>This configuration is based on research and everyday Flutter/Dart development needs.</p><p>It avoids aggressive automation, keeps formatting predictable, and improves readability in large widget trees.</p><p>If you’re looking for a clean and reliable VS Code setup for Flutter and Dart, this is a great place to start.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fba37f050bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Change Flutter App Icons (iOS & Android) — A Quick Reminder]]></title>
            <link>https://medium.com/@ozyurek.aydanil/how-to-change-flutter-app-icons-ios-android-a-quick-reminder-7d1336b65724?source=rss-4629de7d7b61------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d1336b65724</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[android-development]]></category>
            <category><![CDATA[mobile-development]]></category>
            <dc:creator><![CDATA[Ayda Nil Ozyurek]]></dc:creator>
            <pubDate>Tue, 03 Feb 2026 13:25:46 GMT</pubDate>
            <atom:updated>2026-02-03T22:18:58.627Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-C6t6B5Ni4FIoNwX4_ccBQ.png" /></figure><h3>How to Change Flutter App Icons (iOS &amp; Android) — A Quick Reminder</h3><p>Changing Flutter app icons for iOS and Android can be confusing, especially when you haven’t done it in a while.<br>This article is a <strong>quick, step-by-step guide</strong> on how to change Flutter app icons without overthinking the process.</p><p>I wrote it as a reminder for myself — but it should work just as well if you’re setting up a new Flutter project.</p><h3>Why I’m Writing This</h3><p>Every time I create a new Flutter project, I hit the same moment:</p><blockquote>“Okay… how did I change the app icon again?”</blockquote><p>I know I’ve done it before.<br>I know it’s not hard.<br>But somehow, I always forget the exact steps.</p><p>So this article is mainly a <strong>note to my future self</strong> — and if you’re reading this, you probably had the same moment too.</p><p>I’m on <strong>macOS</strong>, and I’ll explain both <strong>iOS</strong> and <strong>Android</strong> setups using Flutter.</p><h3>Step 1: Prepare Your App Icon</h3><p>First things first — you need <strong>one clean, high-resolution app icon image</strong>.</p><p>Before uploading, make sure that:</p><ul><li>The image is <strong>square</strong> (preferably <strong>1024×1024 px</strong>)</li><li>There are <strong>no rounded corners</strong> (platforms handle that)</li><li>There’s <strong>no transparent background</strong> (unless you really know what you’re doing)</li><li>The design is <strong>simple</strong> (icons are small in real life)</li></ul><p>Once your image is ready, go to:</p><p>👉 <a href="https://www.appicon.co/"><strong>https://www.appicon.co/</strong></a></p><h3>Step 2: Generate Icons with AppIcon.co</h3><ol><li>Upload your app icon image to <strong>appicon.co</strong></li><li>Select the platforms you need:</li></ol><ul><li>✅ iOS</li><li>✅ Android</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*M7_SEGWgg_Zh2pTAXCUgqw.png" /></figure><p>3. Click <strong>Generate</strong></p><p>The website will automatically:</p><ul><li>Resize your icon for all required dimensions</li><li>Organize everything into proper folders</li><li>Generate a <strong>ZIP file</strong></li></ul><p>Download the ZIP file — we’ll use it for both platforms.</p><p>Up to this point, everything is platform-agnostic and super easy.</p><h3>Step 3: Change App Icon for iOS (Flutter)</h3><ol><li>In <strong>VS Code</strong>, under the ios folder, <strong>right-click </strong><strong>Runner → “Reveal in Finder.”</strong></li><li>In Finder, <strong>delete the existing </strong>Assets.xcassets<strong> folder.</strong></li><li>From <strong>appicon.co</strong>, copy the generated Assets.xcassets folder and <strong>paste it into the </strong>Runner<strong> directory.</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/296/1*VyMwefnh3hvuPvRL7oENMQ.png" /><figcaption>After completing all steps, your iOS app icon setup should look like this — with all generated icon sizes correctly placed under ios → Runner → Assets.xcassets</figcaption></figure><p>Run the app to see the updated <strong>Flutter iOS app icon</strong>.</p><h3>Step 4: Change App Icon for Android (Flutter)</h3><p>Open: android → app → src → main → res</p><p>Inside res, <strong>select all </strong><strong>mipmap-* folders</strong> and <strong>delete them</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/647/1*mfsBojmNnhrCNwvwbsMN9g.png" /></figure><p>From the ZIP generated by <strong>appicon.co</strong>, copy the <strong>Android </strong><strong>mipmap-* folders</strong> and <strong>paste them into</strong> the same res directory (replacing what you deleted).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*-wicwVSba8RUtrB0DXbiew.png" /></figure><p>Run the app to see the updated <strong>Flutter Android app icon</strong>.</p><p>If you’ve followed all the steps, your <strong>Flutter app icon</strong> should now be correctly updated on <strong>both iOS and Android</strong>.</p><p>No extra tools, no hidden configuration — just a clean and simple setup that works every time.</p><p>This was mainly a <strong>note to my future self</strong>, but if it saved you a few minutes while setting up a new Flutter project, then it did its job.</p><p>Happy coding 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d1336b65724" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flutter Android Build Failed Because of a Broken NDK]]></title>
            <link>https://medium.com/@ozyurek.aydanil/flutter-android-build-failed-because-of-a-broken-ndk-baabec961c94?source=rss-4629de7d7b61------2</link>
            <guid isPermaLink="false">https://medium.com/p/baabec961c94</guid>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[android-development]]></category>
            <category><![CDATA[mobile-development]]></category>
            <dc:creator><![CDATA[Ayda Nil Ozyurek]]></dc:creator>
            <pubDate>Sun, 25 Jan 2026 20:10:59 GMT</pubDate>
            <atom:updated>2026-01-25T20:10:59.177Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p3bSOWVL83miCqPLVzEm5Q.png" /></figure><p>While setting up a new Flutter project on macOS, I ran into an Android build error that completely blocked the app from running.<br>It looked serious at first, but the fix turned out to be much simpler than expected.</p><p>If you’re seeing an NDK-related error and wondering whether your Flutter or Gradle setup is broken — it probably isn’t.</p><h3>The error</h3><p>During flutter run, Android build failed with the following message:</p><pre>[CXX1101] NDK did not have a source.properties file</pre><p>At this point, it’s easy to assume something is wrong with Gradle, Flutter, or even your project configuration.</p><h3>Why this happens</h3><p>This error usually means that the <strong>Android NDK was downloaded incompletely</strong>.<br>Android Studio sometimes leaves the NDK in a broken state, missing the source.properties file that Gradle expects.</p><p>This is a <strong>tooling issue</strong>, not a Flutter code problem.</p><h3>The fix (macOS)</h3><p>First, delete the broken NDK folder from your machine:</p><pre>rm -rf ~/Library/Android/sdk/ndk/28.2.13676358</pre><p>(Replace the version number if yours is different.)</p><p>Then:</p><ol><li>Open <strong>Android Studio</strong></li><li>Go to <strong>Settings → Android SDK → SDK Tools</strong></li><li>Enable <strong>NDK (Side by side)</strong></li><li>Apply and let Android Studio re-download it</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fEyB3vinKZjVcYtspP0wAw.png" /></figure><p>After that, run:</p><pre>flutter clean<br>flutter pub get<br>flutter run</pre><p>The build should succeed normally.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=baabec961c94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why VS Code Can’t Update on macOS]]></title>
            <link>https://medium.com/@ozyurek.aydanil/why-vs-code-cant-update-on-macos-0ec5a3afbcbb?source=rss-4629de7d7b61------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ec5a3afbcbb</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[visual-studio-code]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ayda Nil Ozyurek]]></dc:creator>
            <pubDate>Sun, 25 Jan 2026 17:41:36 GMT</pubDate>
            <atom:updated>2026-01-25T17:42:08.506Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lijaa8rzd9iVItMFlbi3ZA.png" /></figure><p>VS Code refusing to update on macOS with a “read-only volume” error? Here’s why it happens — and how to fix it in under 2 minutes.</p><p>If you’re using <strong>Visual Studio Code on macOS</strong> and suddenly see this error:</p><pre>Cannot update while running on a read-only volume. <br>The application is on a read-only volume. <br>Please move the application and try again. <br>If you&#39;re on macOS Sierra or later, you&#39;ll need to move the application <br>out of the Downloads directory. <br>This might mean the application was put on quarantine by macOS.</pre><p>You’re not alone.<br>This is a <strong>very common macOS + VS Code issue</strong>, especially for developers setting up Flutter, Xcode, or extensions.</p><h3>Why does this happen?</h3><p>Starting from <strong>macOS Sierra</strong>, Apple introduced stricter security rules:</p><ul><li>Apps downloaded from the internet are marked as <strong>quarantined</strong></li><li>Apps launched from the Downloads folder may behave like they’re on a <strong>read-only volume</strong></li></ul><blockquote><strong>A read-only volume</strong> is a protected location on macOS where apps can run but <strong>cannot modify or update themselves</strong>, which is why VS Code fails to update when launched from places like the Downloads folder.</blockquote><ul><li>VS Code tries to self-update → macOS blocks it</li><li>Even if you later move VS Code to /Applications, the quarantine flag may still remain.</li></ul><h3>Let’s Fix It Step by Step</h3><p>1. Make sure VS Code is in /Applications</p><ul><li>Quit VS Code completely (Cmd + Q)</li><li>Open Finder → <strong>Applications</strong></li><li>Confirm Visual Studio Code.app is there<br> (If it’s still in Downloads → move it and delete the old copy)</li></ul><p>2. Remove the macOS quarantine flag</p><ul><li>Open <strong>Terminal</strong> and run:</li></ul><pre>xattr -rd com.apple.quarantine /Applications/Visual\ Studio\ Code.app</pre><ul><li>If nothing is printed, it worked.</li></ul><p>This removes macOS’s <strong>“downloaded from the internet”</strong> restriction.</p><p>3. Reopen VS Code</p><ul><li>Open VS Code from <strong>Applications</strong></li><li>Try: Cmd + Shift + P → Check for Updates</li></ul><p>🎉 The error should be gone.</p><h3>⚠ Common mistakes</h3><ul><li>Running VS Code <strong>directly from the DMG</strong></li><li>Opening it <strong>from Downloads</strong></li><li>Having <strong>two VS Code copies</strong> (one in Downloads, one in Applications)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ec5a3afbcbb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>