<?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 Ayseleynavuz on Medium]]></title>
        <description><![CDATA[Stories by Ayseleynavuz on Medium]]></description>
        <link>https://medium.com/@ayseleynavuz?source=rss-6a74e9d70941------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_7xqhXC_0dI13kuDmUXllw.jpeg</url>
            <title>Stories by Ayseleynavuz on Medium</title>
            <link>https://medium.com/@ayseleynavuz?source=rss-6a74e9d70941------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:25:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ayseleynavuz/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[To Anyone Saying “Flutter Is Dead”: Here’s Why It’s Still the Smartest Mobile Investment in 2026]]></title>
            <link>https://medium.com/@ayseleynavuz/to-anyone-saying-flutter-is-dead-heres-why-it-s-still-the-smartest-mobile-investment-in-2026-81310ed3da07?source=rss-6a74e9d70941------2</link>
            <guid isPermaLink="false">https://medium.com/p/81310ed3da07</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <dc:creator><![CDATA[Ayseleynavuz]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 16:01:23 GMT</pubDate>
            <atom:updated>2026-06-04T16:01:23.283Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bN5z1TE_4s3r2NIfNtLZ0Q.png" /></figure><h3>The truth behind the big-company migration myths, the overrated “native” hype, and Flutter’s unshakeable throne in modern mobile architecture.</h3><p>The tech world loves two things: hyping a new framework to the moon, and writing its obituary a few years later.</p><p>Lately, if you’ve been scrolling through Medium, LinkedIn, or Reddit, you’ve probably seen the headlines: <em>“Company X moved away from Flutter,”</em> <em>“Scale-up Y is migrating to React Native,”</em> or <em>“Is it the end of the road for Flutter?”</em></p><p>As a Flutter Developer, whenever I see these articles, I just lean back and smile. Why? Because these narratives usually mask poor management decisions, flawed architectural choices, or engineering mistakes, using the framework as a convenient scapegoat.</p><p>Let’s look past the “silent migration” myth and separate the hype from reality. Here is why Flutter remains the most powerful, cost-effective, and strategically sound choice for building a mobile product in 2026.</p><h3>1. The “Performance Ceiling” Myth and the Impeller Reality</h3><p>For years, native purists held onto a single argument: “shader compilation jank” — those micro-stutters that used to occur when a Flutter app initialized screens for the first time.</p><p>With Google’s <strong>Impeller rendering engine</strong> now fully active and mature, that argument is technically dead. Impeller pre-compiles shaders and renders pixels directly on the GPU, delivering a flawless, buttery-smooth 120 FPS experience.</p><p>Today, it is virtually impossible for an end-user to distinguish between a pure native app and a well-optimized Flutter app. If a Flutter app is lagging, the fault doesn’t lie with the framework; it lies in a poorly designed architecture that mishandles State Management or chokes the main thread with asynchronous operations. Bad code stutters in Swift and Kotlin just as much as it does in Dart.</p><h3>2. What Those “Migration Stories” Are Actually Telling You</h3><p>When you dig beneath the surface of stories where a massive corporation “abandoned” Flutter, you almost always find the same scenario: <strong>Brownfield (Hybrid) Architectures.</strong></p><p>If you try to patch Flutter into a massive, legacy, million-line native codebase as an afterthought, you are going to encounter friction. Building and maintaining extensive platform channels to bridge the native host app and the Flutter engine eventually creates architectural overhead.</p><p>But that isn’t a failure of Flutter; it’s a consequence of a mismatched architectural strategy. On the flip side, companies that start fresh (“Greenfield”) or structure their modular architecture correctly — like digital banking giants such as Nubank — successfully manage billions in transaction volume from a unified Flutter codebase with hundreds of engineers. If structured correctly from day one, Flutter never bottlenecks your scale.</p><h3>3. The Power of Ecosystem and a Single, Robust Language</h3><p>A common argument from the opposing camp is: <em>“Let’s use React Native so our web team can share JavaScript/TypeScript code.”</em></p><p>While that sounds like a great management philosophy on paper, in practice, it often leads to products that run sub-optimally on both platforms. JavaScript’s asynchronous nature and bridge-dependent architecture have historically acted as a handbrake for mobile performance.</p><p><strong>Dart</strong>, on the other hand, is a masterpiece designed for modern, object-oriented client development. With strong typing, sound null safety, and AOT (Ahead-of-Time) compilation, it communicates directly with the device hardware. Sacrificing mobile application performance just to let your web team speak the same language is a trade-off that costs more in the long run.</p><h3>4. Real-World Economics: Time-to-Market and Velocity</h3><p>In product management and entrepreneurship, there is only one golden rule: <strong>Speed wins.</strong></p><p>Building the exact same application twice — once in Swift for iOS and once in Kotlin for Android — means hiring two separate teams, fixing the same bugs in two different codebases, and burning double the budget.</p><p>Flutter delivers <strong>native performance</strong> from a single, clean codebase. The sheer product velocity of writing a UI change or a business logic update once, and shipping it to both stores on the same day (Time-to-Market), can be the difference between a startup surviving or folding.</p><p>Furthermore, the pub.dev ecosystem is incredibly rich. Integrations that would take days to wire up natively can be implemented in Flutter in a matter of hours, making your product production-ready at a fraction of the time.</p><h3>The Verdict: Maturity, Not Mortality</h3><p>Flutter isn’t dying; it is maturing. It has shed its childhood hype and solidified into a proven, reliable industry standard.</p><p>Backed by Google’s ongoing engineering commitment, powered by the revolutionary performance of Impeller, and sustained by a massive global community, Flutter continues to shape the future of mobile development.</p><p>Don’t let the corporate grapevine fool you. In the right hands, with the right architecture, a Flutter application is the most profitable, secure, and future-proof tech stack decision a company can make. And as a Flutter Developer, I’m proud to be building that future every single day.</p><h3>What Are Your Thoughts?</h3><p><em>Do you agree that Flutter’s development velocity and performance are still unmatched in cross-platform development? Share your project experiences in the comments below!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81310ed3da07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Request an Expedited App Store Review (Quick Guide 2025)]]></title>
            <link>https://medium.com/@ayseleynavuz/how-to-request-an-expedited-app-store-review-quick-guide-2025-eeaa06895ca3?source=rss-6a74e9d70941------2</link>
            <guid isPermaLink="false">https://medium.com/p/eeaa06895ca3</guid>
            <category><![CDATA[apple-review]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[app-store]]></category>
            <category><![CDATA[mobil-uygulama]]></category>
            <dc:creator><![CDATA[Ayseleynavuz]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 15:00:39 GMT</pubDate>
            <atom:updated>2025-12-15T15:00:39.701Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vK3TRhrwi1mR9AZvbYRtdA.png" /></figure><p><strong>“You’ve rolled out the latest version to 100% of your users. Two hours later, you realize the app crashes on launch. Apple approval typically takes 24–48 hours. How do you manage this crisis instantly?”</strong></p><p>This scenario is every iOS Developer or Product Manager’s worst nightmare.</p><p>Under normal circumstances, App Store review times have improved significantly in recent years (usually taking 24–48 hours). However, sometimes this window is too long, or you need to get that update live <strong>right now</strong>.</p><p>This is exactly where the <strong>“Expedited Review”</strong> comes into play. Let’s explore how to navigate this process, keeping in mind the 2025 updates and Apple’s current sensitivities.</p><h3>What is an Expedited Review?</h3><p>Simply put, it is a request to bump your app to the front of the review queue. If you have a valid reason, Apple will prioritize your submission over others.</p><blockquote><strong><em>⚠️ Important Warning:</em></strong><em> Treat this option like a “Joker card” or a “Break Glass in Case of Emergency” button. If you use it too frequently, Apple may start ignoring your requests. Use it only for genuine emergencies.</em></blockquote><h3>When Should You Request It?</h3><p>As of 2025, Apple remains quite strict about this. <em>“My manager wants this live by tomorrow”</em> is <strong>not</strong> a valid reason.</p><p>There are generally three accepted scenarios:</p><ol><li><strong>Critical Bug Fixes:</strong> Issues that cause crashes, data loss, or render the app unusable for users.</li><li><strong>Time-Sensitive Events:</strong> Updates tied to specific dates (product launches, marketing campaigns, sports events, legal obligations).</li><li><strong>Legal or Safety Issues:</strong> Updates required to comply with immediate legal actions.</li></ol><p><em>Routine updates or minor UI tweaks will not qualify.</em></p><h3>How to Request It (Step-by-Step)</h3><h3>1. Prepare Your Build</h3><p>First, upload your binary to App Store Connect and ensure the status is <strong>“Waiting for Review”</strong>. Note down your specific <strong>Version</strong> and <strong>Build Number</strong>.</p><h3>2. Go to the Contact Form</h3><p>Navigate directly to Apple’s developer contact page:</p><ul><li><a href="https://developer.apple.com/contact/app-store/?topic=expedite">App Store Connect Contact Us</a></li><li><a href="https://developer.apple.com/contact/app-store/?topic=expedite">https://developer.apple.com/contact/app-store/?topic=expedite</a></li></ul><h3>3. Select the Correct Topic</h3><p>On the page, follow this path: <strong>App Review</strong> &gt; <strong>Request Expedited App Review </strong>Then, click the <strong>“Contact App Review”</strong> button.</p><h3>4. Fill Out the Form</h3><p>You will need to provide:</p><ul><li><strong>Contact Information:</strong> Name, Email.</li><li><strong>App Information:</strong> App Name, Apple ID (found in the App Information section of App Store Connect), Platform (iOS).</li><li><strong>Description:</strong> This is the most critical part.</li></ul><h3>The Request Template (Copy-Paste Ready)</h3><p>To increase your chances of approval, be clear, polite, and technical. Don’t write a story; focus on the problem and the user impact.</p><p>Template for a Critical Bug Fix , <strong>Select Reason:</strong> Critical Bug Fix</p><pre>Dear App Review Team,<br><br>We have discovered a critical crash affecting [XX]% of our users on iOS [Version].<br>The app crashes immediately upon [Login/Opening a specific screen],<br>rendering the app unusable.<br><br>We have fixed this issue in the submitted build (Version X.X.X, Build XXX).<br>Since this severely impacts our user experience and data integrity,<br>we kindly request an expedited review to release the fix as soon as possible.<br><br>Steps to reproduce the crash are included in the review notes.<br><br>Thank you for your support.</pre><h3>Conclusion: What to Expect?</h3><p>After submitting the form, you will usually receive an automated “Request Received” email within <strong>1–2 hours</strong>.</p><ul><li><strong>If Approved:</strong> Your app is typically reviewed and approved within <strong>12–24 hours</strong> following the request.</li><li><strong>If Rejected:</strong> You will have to wait for the standard review cycle.</li></ul><p>Remember, an Expedited Review is <strong>a privilege, not a right</strong>. Use this process wisely and only when absolutely necessary. Good luck! 🚀</p><p><strong>References &amp; Further Reading:</strong></p><ul><li><a href="https://www.reddit.com/r/iOSProgramming/comments/1inv01k/expedited_review_is_very_fast_i_was_able_to_push/">Reddit Discussion on 2025 Review Times</a></li><li><a href="https://www.polpiella.dev/expedited-app-reviews">Polpiella: Expedited App Reviews Guide</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eeaa06895ca3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Karar Ağaçları (Decision Tree) ve Kademeli Kırılımlar]]></title>
            <link>https://medium.com/@ayseleynavuz/karar-a%C4%9Fa%C3%A7lar%C4%B1-decision-tree-ve-kademeli-k%C4%B1r%C4%B1l%C4%B1mlar-4ba813e99197?source=rss-6a74e9d70941------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ba813e99197</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[veri-bilimi]]></category>
            <category><![CDATA[decision-tree]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Ayseleynavuz]]></dc:creator>
            <pubDate>Wed, 04 Jun 2025 14:16:56 GMT</pubDate>
            <atom:updated>2025-06-04T14:16:56.511Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*6iKs98HZ72J-rmDp.png" /></figure><p>Veri bilimi dünyasında karar ağaçları, veriyi gruplara ayırarak tahmin yapmayı sağlayan oldukça sezgisel modellerdir. Bu yazıda karar ağaçlarının temel mantığını basit bir örnekle açıklayacağım.</p><p>Adım 1: Veri Seti ile Başlayalım</p><pre>import pandas as pd<br>from math import sqrt<br><br>oyuncular = {<br>    &quot;boy&quot;: [175, 177, 178, 181, 182, 183, 184, 188, 190], <br>    &quot;deneyim&quot;: [4, 6, 3, 2, 6, 3, 7, 2, 6],<br>    &quot;maas&quot;: [12, 18, 15, 16, 24, 20, 28, 24, 32]<br>}<br><br>df = pd.DataFrame(oyuncular)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/177/1*qBW6-eI_hxla8aBrCTm85w.png" /></figure><p>Adım 2: Ortalama ile Başlayan Basit Model (Mean Model)</p><p>İlk olarak en basit modeli kuruyoruz: herkesin maaşı aynıymış gibi davranıyoruz. Bu model bize bir “referans hata” verir.</p><pre>df.maas.mean()<br># output: 21.0</pre><p>Bu modelde herkesin maaşı 21 gibi kabul edilir. Bu modele <strong>Mean Model</strong> (ortalama modeli) denir. Herhangi bir özelliği (boy, deneyim) dikkate almaz.</p><p>Bu modelin toplam hatasını (train error) hesaplayalım. Negatif çıkmaması için karesini alıyoruz.</p><pre>(df.maas - df.maas.mean()).pow(2).sum()<br># output: 340.0</pre><h3>Adım 3: İlk Kırılım — Boy Bilgisine Göre</h3><p>Veri setimizi boylarına göre ikiye ayıralım:</p><ul><li>180 cm ve altı (kısa oyuncular)</li><li>180 cm’den uzun olanlar</li></ul><p>≤180 ve &gt;180 dataframe1 ve dataframe2 diye böldük. Buna kategorik ortalama model deniliyor.</p><p>180 den kısa olanları true, diğerlerini false olacak şekilde pandas serisi döndürecek. ~ tilda işaretini, değilini almak için kullanıyoruz.</p><pre>filt = (df.boy &lt;= 180)<br>df1 = df[filt]  #df1 180den kısa olanlar<br>df2 = df[~filt] #df2 180den uzun olanlar</pre><p>Bu grupların ortalama maaşlarına bakalım:</p><pre>df1.maas.mean()  # 15.0<br>df2.maas.mean()  # 24.0</pre><p>Train Error Hesaplama (validation veya test yok) kırılım yaptıkça azalacak mı buna bakıyoruz.</p><pre>(df1.maas - df1.maas.mean()).pow(2).sum() + <br>(df2.maas - df2.maas.mean()).pow(2).sum()<br># output: 178.0</pre><p>Gördüğünüz gibi, tek bir kırılım bile hatayı 340’tan 178’e düşürdü.</p><p>Adım 4: İkinci Kırılım — Boy Bilgisine Devam</p><p>180 cm’den uzun oyuncular grubunu (df2) tekrar bölelim. (df2) 180 den uzun olan kişilerdi zaten. Şimdi ikinci filtreyi uygulayacağız. 180&#39;den uzun olanları 185&#39;ten kısa mı?</p><pre>filt2 = (df2.boy &lt;= 185)<br>df3 = df2[filt2]<br>df4 = df2[~filt2]</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/193/1*nl3oKi3-rsb5Eg1Pv4E7lQ.png" /><figcaption>df4</figcaption></figure><p>Ortalama maaşlar:</p><pre>df3.maas.mean()  # 22.0<br>df4.maas.mean()  # 28.0</pre><p>İkinci Bölme Error Hesabı</p><pre>(df1.maas - df1.maas.mean()).pow(2).sum() + <br>(df3.maas - df3.maas.mean()).pow(2).sum() +<br>(df4.maas - df4.maas.mean()).pow(2).sum()<br># output: 130.0</pre><p>Not: Ana veri setini başta ikiye böldük : df1 180’ den kısalar, df2 180’ den uzun olanlar,</p><p>180 den uzunları da ikiye böldük: df3 180 den uzun olup 185&#39;ten kısa olanlar, df4 180 den uzun olup 185&#39;ten kısa olmayan.</p><p>Toplamda elimizde 3 veri seti olduk. Toplamda 3 tahminde bulunduk.</p><p>Hiç kırılım yapmadan 340, bir kırılım yaparak 178, İki kırılım yaparak 130 sonucunu elde ettik.</p><p>180≤df2 , df1≤180 , 180≤df3&lt;185</p><p>Adım 5: Üçüncü Kırılım — Bu Sefer Deneyim!</p><p>180 &lt; boy ≤ 185 olan oyuncuları (df3) deneyimlerine göre ikiye bölelim:</p><pre>filt3 = (df3.deneyim &lt;=5)<br>df5 = df3[filt3]<br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/195/1*dJNcDVnrSEO9VY45rmKqYw.png" /><figcaption>df5</figcaption></figure><pre>df6 = df3[~filt3]</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/195/1*dabkXBrg2KHFRR6NgV5bgw.png" /><figcaption>df6</figcaption></figure><p>Ortalamasına Bakalım</p><pre>df5.maas.mean()  # 18.0<br>df6.maas.mean()  # 26.0</pre><p>Üçüncü Bölme Error’u</p><pre>(df1.maas - df1.maas.mean()).pow(2).sum() + <br>(df4.maas - df4.maas.mean()).pow(2).sum() + <br>(df5.maas - df5.maas.mean()).pow(2).sum() + <br>(df6.maas - df6.maas.mean()).pow(2).sum()<br># output: 66.0</pre><h3>Gözlem</h3><ul><li>Başlangıçtaki ortalama modele ait hata: <strong>340.0</strong></li><li>Birinci kırılım sonrası hata: <strong>178.0</strong></li><li>İkinci kırılım sonrası hata: <strong>130.0</strong></li><li>Üçüncü kırılım sonrası hata: <strong>66.0</strong></li></ul><p>Her kırılımda hata azaldı. Karar ağacının temel amacı da budur: veriyi uygun şekilde bölerek tahmin hatasını azaltmak.</p><h3>Peki, En İyi Soruyu Nasıl Seçeriz?</h3><p>Karar ağacı algoritmaları (CART, ID3, C4.5 vs.) her özellik ve eşik değeri için kırılım dener ve en düşük hatayı (veya en yüksek bilgi kazancını) veren bölmeyi seçer.</p><p>Her özelliğin tüm <strong>unique</strong> değerleri denenir. Aynı sorunun tekrar sorulmaması için daha önce uygulanan kırılımlar dikkate alınır.</p><h3>Sonuç</h3><p>Bu yazıda karar ağacının temellerini, veri setini nasıl bölerek hata azaltabileceğimizi ve karar noktalarının nasıl belirlendiğini gördük. Gerçek dünyada bu işlemler otomatikleştirilir ve çok daha büyük veri setleriyle yapılır. Ama temeli anlamak, modelin neden böyle çalıştığını kavramak için bu tarz örnekler çok önemlidir.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*MapToKPL1olNYh92.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ba813e99197" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Veri Bilimi Nedir, Ne Değildir? — Kahve, Netflix ve Biraz Da Matematik]]></title>
            <link>https://medium.com/@ayseleynavuz/veri-bilimi-nedir-ne-de%C4%9Fildir-kahve-netflix-ve-biraz-da-matematik-de7bf62cd2f7?source=rss-6a74e9d70941------2</link>
            <guid isPermaLink="false">https://medium.com/p/de7bf62cd2f7</guid>
            <category><![CDATA[verianalizi]]></category>
            <category><![CDATA[veri-bilimi]]></category>
            <category><![CDATA[yazılım]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Ayseleynavuz]]></dc:creator>
            <pubDate>Thu, 22 May 2025 14:03:35 GMT</pubDate>
            <atom:updated>2025-05-22T14:03:35.546Z</atom:updated>
            <content:encoded><![CDATA[<h3>Veri Bilimi Nedir, Ne Değildir? — Kahve, Netflix ve Biraz Da Matematik</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*AvgXm1kZdC2CW5eL.jpg" /></figure><blockquote><em>“Veri bilimi öğrenmek istiyorum ama çok mu karışık acaba?”</em></blockquote><blockquote><em>“Matematik bilmem lazım mı?”</em></blockquote><blockquote><em>“Kod yazmadan da anlayabilir miyim?”</em></blockquote><p>Eğer sen de bu soruları kendine soruyorsan, doğru yerdesin. Çünkü bu yazı sana veri biliminin ne olduğunu, neden bu kadar popüler olduğunu ve aslında ne kadar <strong>sezgisel</strong> bir alan olduğunu göstermek için yazıldı. Hazırsan başlayalım! 🚀</p><h3>1. Bölüm: Veri Bilimine Giriş</h3><p>Sabah kahveni alıp Instagram’da birkaç story’ye baktın, sonra Spotify “Senin için hazırlandı” çalma listesini açtın. Ardından hava durumuna baktın, işe gittin, kredi kartınla kahve aldın.</p><p>Hiç düşündün mü, bu sıradan gününde geride nasıl bir dijital iz bıraktığını?</p><p>İşte veri bilimi tam da bu izleri takip eder. Amaç? Seni tanımak, sana yardımcı olmak… ve bazen de reklam göstermek (üzgünüm).</p><p>Bu yazıda veri bilimi denen o gizemli, havalı ama aslında oldukça mantıklı dünyaya giriş yapıyoruz. Hiç formül kullanmadan, hiç korkutmadan.</p><p>Sadece sorular soracağız, bazılarını cevaplayacağız, bazılarını birlikte merak edeceğiz.</p><h3>2. Bölüm: Veri dediğimiz şey tam olarak ne?</h3><p>Veri dediğimiz şey aslında bir nevi dijital “iz”. Tıpkı çamurlu bir yolda yürürken bıraktığın ayak izleri gibi.<br> Ama bu izler çamurda değil; telefonda, bilgisayarda, market fişinde, kamerada.</p><ul><li>Sabah kahveni aldığında saat kaçtı?</li><li>Spotify’da hangi şarkıyı dinledin, kaçı saniye sürdü?</li><li>Yürürken kaç adım attın?</li><li>Fotoğraf paylaşırken hangi filtreyi kullandın?</li></ul><p>Tüm bunlar <strong>veri</strong>.</p><p>Ama verinin kendisi sadece “ham madde”. Tıpkı buğday gibi. Veri bilimi ise bu buğdayı alıp un yapıyor, sonra ekmek yapıyor… Ve o ekmeği Netflix “Sana şu filmi öneriyorum” diye sıcak sıcak getiriyor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*rIjieI1EaJ5_PMYk.gif" /></figure><h3>3. Bölüm: Veri Bilimi dediğimizde neyi kastediyoruz?</h3><p>Veri bilimi, verileri alıp “bir işe yarayan bilgiye” dönüştürme sanatıdır.<br> Bu biraz dedektiflik, biraz istatistik, biraz da sabır işidir. Veri bilimi şunu sorar:</p><ul><li>“Bu kullanıcı neden bu ürünü aldı?”</li><li>“Bu müşterinin tekrar gelme ihtimali nedir?”</li><li>“Bu e-posta dolandırıcı mı, yoksa amcamın bayram mesajı mı?”</li></ul><p>Tahmin eder, test eder, yanılır, yeniden dener. Amaç <strong>kesin doğruyu</strong> bulmak değil. Amaç, <strong>mümkün olan en iyi tahmini</strong> yapabilmek.</p><h3>4. Bölüm: Veri Bilimci Ne Yapar? — Bir Kafe Örneğiyle Anlatalım</h3><p>Diyelim ki bir kafede veri bilimcisin. Patron geldi ve dedi ki: <em>“Müşterilerin kahve tercihlerini anlamam lazım. Kim ne zaman ne içiyor?”</em></p><p>Sen de oturdun, verileri topladın: Saat,içilen kahve türü, hava durumu, sipariş uygulaması mı yoksa direkt mi geldi?</p><p>Sonra fark ettin ki:</p><ul><li>Soğuk günlerde latte siparişi artıyor.</li><li>Akşamları daha fazla espresso tercih ediliyor.</li><li>Yeni gelen müşterilerin %80’i indirim koduyla geliyor ama ikinci kez pek gelmiyorlar.</li></ul><p>Tebrikler! Verileri okudun, anlamlı hale getirdin, öneri sundun. İşte bu, <strong>veri bilimciliğin küçük bir yansıması.</strong></p><h3>5. Bölüm: Veri Bilimi Büyü Değildir!</h3><p>Bir yanlış anlaşılmayı burada aradan çıkaralım: Veri bilimi, <strong>her şeyi bilen sihirli bir kutu değildir. </strong>Tahminler bazen tutar, bazen tutmaz. Örneğin hava durumu uygulaması “yağmur yağacak” der ama güneş açabilir. Bu yanlışsa “veri bilimi kötü” değildir. Sadece model daha iyi öğrenmeye ihtiyaç duyuyordur.</p><p>Veri bilimci bir falcı değildir. Ama çok iyi bir tahmin ustasıdır.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/0*Z3kxadpnO8vzvpv6.jpeg" /></figure><h3>6. Bölüm: Veri Bilimi Günlük Hayatta Nerede Karşımıza Çıkıyor?</h3><p>Daha farkında bile olmadan, her gün onlarca kez veri biliminin sonuçlarıyla karşılaşıyoruz. İşte bazı “görünmez veri bilimciler”:</p><h4>🎬 Netflix — Ne İzleyeceğini Nereden Biliyor?</h4><p>Netflix senin neler izlediğini, hangi sahnede durdurduğunu, hangi türleri sevdiğini takip ediyor. Sonra da benzer davranışları olan milyonlarca kişiye bakıyor. “Bu kişi şu diziyi sevdiyse, büyük ihtimalle bunu da sevecektir” diyerek öneri sunuyor.</p><p>Buna <strong>öneri sistemi</strong> deniyor. Ve veri biliminin en eğlenceli alanlarından biri!</p><h4>💌 Spam Filtresi — Amcan mı, Dolandırıcı mı?</h4><p>Mail kutundaki spam filtresi, her gelen e-postayı kontrol ediyor:<br> Bazı kelimeler, linkler, gönderici adresleri…<br> “Bu mesajlar genellikle dolandırıcılık içeriyor” diyerek filtreleme yapıyor.</p><p>Yani veri bilimi burada dijital bir güvenlik görevlisi gibi çalışıyor.</p><h4>🏦 Bankalar — Şüpheli Harcamaları Nasıl Anlıyor?</h4><p>Kartınla her zaman İstanbul’da alışveriş yaparken bir anda Brezilya’dan işlem görünce bankan hemen uyarı verir. Çünkü sistem, senin “alışveriş alışkanlıklarını” biliyor. Bu alışkanlık dışı bir davranışsa, şüpheleniyor. Belki kartın çalındı, kim bilir?</p><p>İşte bu da veri biliminin <strong>anormallik tespiti</strong> dediğimiz bir uygulaması.</p><h4>🧠 Spotify — Yeni Şarkılara Nasıl Karar Veriyor?</h4><p>Spotify sana “Senin için hazırlandı” listesi sunarken, senin müzik zevkini öğrenmeye çalışıyor. Sadece dinlediğin şarkılar değil, ne zaman dinlediğin, ne kadar dinlediğin bile önemli.</p><p>Yani bazen gece 2’de açtığın hüzünlü şarkılar, algoritmanın ruh halini bile anlayabileceği günlere doğru bizi götürüyor. 🎧😅</p><h3>7. Bölüm: Peki Sen Ne Tahmin Etmek İsterdin?</h3><p>Veri bilimi aslında insana dair bir şey. İnsan davranışlarını, tercihlerini, alışkanlıklarını anlamaya çalışıyor. Kimi zaman “Bu müşteri tekrar gelir mi?” diye soruyoruz. Kimi zaman “Bu film ona hitap eder mi?” diyoruz. Bazen de “Bu uygulama bağımlılık yaratır mı?” gibi daha etik sorularla uğraşıyoruz.</p><p>Ve şimdi sana soralım… <em>Eğer elinde milyonlarca satır veri olsaydı…</em></p><p>Ne sorardın? Ne öğrenmek isterdin? Geleceği mi tahmin ederdin, yoksa insanların bugününü mü anlamaya çalışırdın?</p><p>→ Senin sorman gereken sorular, belki de henüz kimsenin aklına bile gelmedi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*sXQUQpMYRKrz1frE.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de7bf62cd2f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flutter Send Push Notification Firebase Cloud Messaging API (V1) | New FCM API OAuth2]]></title>
            <link>https://medium.com/@ayseleynavuz/flutter-send-push-notification-firebase-cloud-messaging-api-v1-new-fcm-api-oauth2-82e292ecf55c?source=rss-6a74e9d70941------2</link>
            <guid isPermaLink="false">https://medium.com/p/82e292ecf55c</guid>
            <category><![CDATA[firebasecloudmessaging]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[oauth2]]></category>
            <dc:creator><![CDATA[Ayseleynavuz]]></dc:creator>
            <pubDate>Tue, 04 Feb 2025 12:24:41 GMT</pubDate>
            <atom:updated>2025-02-04T12:24:41.961Z</atom:updated>
            <content:encoded><![CDATA[<p>PHP + FLUTTER + HTTP v1 API</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wcwzPFLvi5tUtnce3osUMA.png" /></figure><p>You need to use the HTTP v1 API instead of the old FCM APIs. To do this, you will need to generate a JWT token before each request and use a service account to initialize Firebase services. To create this service account and obtain the JWT token, you will need the service-account.json file.<br>You will need to create a service account and use the service-account.json file to generate the JWT token and utilize Firebase services. Here’s a step-by-step guide on how you can do it:</p><h3>Creating a Service Account in Firebase:</h3><ol><li>Go to the Firebase Console.</li><li>Select your project.</li><li>From the left menu, click on <strong>Project settings</strong>.</li><li>Navigate to the <strong>Service accounts</strong> tab.</li><li>Click the <strong>Generate new private key</strong> button. This will create a service account key that will be provided as a JSON file.</li><li>Download the JSON file to your computer and store it in a secure location.</li></ol><h3>Flutter code will look something like this</h3><pre>import &#39;dart:developer&#39;;<br><br>import &#39;package:easy_localization/easy_localization.dart&#39;;<br>import &#39;package:firebase_core/firebase_core.dart&#39;;<br>import &#39;package:firebase_messaging/firebase_messaging.dart&#39;;<br>import &#39;package:flutter/material.dart&#39;;<br>import &#39;package:.../firebase_options.dart&#39;;<br>import &#39;package:.../cache/service/local_caching.dart&#39;;<br><br>@immutable<br>final class AppInitialize {<br>  const AppInitialize._();<br><br>  static Future&lt;void&gt; onAppInit() async {<br>    WidgetsFlutterBinding.ensureInitialized();<br>    await EasyLocalization.ensureInitialized();<br><br>    await Firebase.initializeApp(<br>      options: DefaultFirebaseOptions.currentPlatform,<br>    );<br><br>    await LocalCaching.init();<br>    initNotification();<br>    FirebaseMessaging.onBackgroundMessage(_firebaseMessagingBackgroundHandler);<br>  }<br><br>  static void initNotification() async {<br>    FirebaseMessaging messaging = FirebaseMessaging.instance;<br><br>    NotificationSettings settings = await messaging.requestPermission(<br>      alert: true,<br>      announcement: false,<br>      badge: true,<br>      carPlay: false,<br>      criticalAlert: false,<br>      provisional: false,<br>      sound: true,<br>    );<br><br>    if (settings.authorizationStatus == AuthorizationStatus.authorized) {<br>      String? token = await messaging.getToken();<br>      if (token != null) {<br>        log(&#39;Token: $token&#39;);<br>      }<br>      FirebaseMessaging.onMessage.listen((RemoteMessage message) {<br>        log(&#39;Got a message whilst in the foreground!&#39;);<br>        log(&#39;Message data: ${message.data}&#39;);<br><br>        if (message.notification != null) {<br>          log(&#39;Message also contained a notification: ${message.notification}&#39;);<br>        }<br>      });<br>    } else {<br>      log(&#39;User declined or has not accepted permission&#39;);<br>    }<br>  }<br>}<br><br>Future&lt;void&gt; _firebaseMessagingBackgroundHandler(RemoteMessage message) async {<br>  await Firebase.initializeApp(<br>    options: DefaultFirebaseOptions.currentPlatform,<br>  );<br>  log(&quot;Handling a background message: ${message.messageId}&quot;);<br>}</pre><h3>Sending Notification with JWT Token in PHP:</h3><ol><li><strong>Generating JWT Token</strong>: Use the Firebase Admin SDK to generate the JWT token. In PHP, this is usually done by using the Firebase Admin SDK. For example:</li></ol><pre>use Firebase\JWT\JWT;<br>use Firebase\JWT\Key;<br><br>function createJwtToken($serviceAccountKeyFile) {<br>    $keyFile = json_decode(file_get_contents($serviceAccountKeyFile), true);<br>    $privateKey = $keyFile[&#39;private_key&#39;];<br>    $token = [<br>        &quot;iss&quot; =&gt; $keyFile[&#39;client_email&#39;],<br>        &quot;sub&quot; =&gt; $keyFile[&#39;client_email&#39;],<br>        &quot;aud&quot; =&gt; &quot;https://oauth2.googleapis.com/token&quot;,<br>        &quot;iat&quot; =&gt; time(),<br>        &quot;exp&quot; =&gt; time() + 3600,<br>        &quot;scope&quot; =&gt; &quot;https://www.googleapis.com/auth/firebase.messaging&quot;,<br>    ];<br>    return JWT::encode($token, $privateKey, &#39;RS256&#39;);<br>}</pre><p>2. <strong>Sending Push Notification</strong>: After generating the JWT token, you can send a notification to the Firebase Cloud Messaging API by making a POST request:</p><pre>function sendPushNotification($title, $body, $token, $jwtToken) {<br>    $url = &quot;https://fcm.googleapis.com/v1/projects/YOUR_PROJECT_ID/messages:send&quot;;<br>    $fields = [<br>        &quot;message&quot; =&gt; [<br>            &quot;token&quot; =&gt; $token,<br>            &quot;notification&quot; =&gt; [<br>                &quot;title&quot; =&gt; $title,<br>                &quot;body&quot; =&gt; $body,<br>            ],<br>        ],<br>    ];<br>    $headers = [<br>        &quot;Authorization: Bearer $jwtToken&quot;,<br>        &quot;Content-Type: application/json&quot;,<br>    ];<br>    $ch = curl_init();<br>    curl_setopt($ch, CURLOPT_URL, $url);<br>    curl_setopt($ch, CURLOPT_POST, true);<br>    curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);<br>    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);<br>    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);<br>    curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode($fields));<br>    $result = curl_exec($ch);<br>    if ($result === FALSE) {<br>        die(&#39;Curl failed: &#39; . curl_error($ch));<br>    }<br>    curl_close($ch);<br>    return $result;<br>}</pre><p>Docs:</p><p>[1] <a href="https://firebase.google.com/docs/cloud-messaging/migrate-v1">https://firebase.google.com/docs/cloud-messaging/migrate-v1</a></p><p>[2] <a href="https://stackoverflow.com/questions/78542180/error-while-enabling-cloud-messaging-api-legacy-in-the-firebase-console">https://stackoverflow.com/questions/78542180/error-while-enabling-cloud-messaging-api-legacy-in-the-firebase-console</a></p><p>[3] <a href="https://stackoverflow.com/questions/65633126/generating-oauth-token-for-firebase-cloud-messaging-php">https://stackoverflow.com/questions/65633126/generating-oauth-token-for-firebase-cloud-messaging-php</a></p><p>[4] <a href="https://developers.google.com/identity/protocols/oauth2/service-account?hl=tr#httprest">https://developers.google.com/identity/protocols/oauth2/service-account?hl=tr#httprest</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82e292ecf55c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing API in Flutter Using MVVM Architecture — Clean Code]]></title>
            <link>https://medium.com/@ayseleynavuz/implementing-api-in-flutter-using-mvvm-architecture-clean-code-53b69cfd9db1?source=rss-6a74e9d70941------2</link>
            <guid isPermaLink="false">https://medium.com/p/53b69cfd9db1</guid>
            <category><![CDATA[flutter-api]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[mvvm-architecture]]></category>
            <category><![CDATA[clean-code]]></category>
            <dc:creator><![CDATA[Ayseleynavuz]]></dc:creator>
            <pubDate>Wed, 24 Jul 2024 17:44:15 GMT</pubDate>
            <atom:updated>2024-07-24T17:44:15.704Z</atom:updated>
            <content:encoded><![CDATA[<h3>Implementing API in Flutter Using MVVM Architecture — Clean Code</h3><p>Hi, we will create a user_api project using Flutter MVVM architecture and writing clean code. I hope you like it. These codes are excerpts from a project I’m working on, and you can customize them according to your needs. I believe you understand the basic logic. I hope it serves your purpose well.</p><p>MVVM Architecture Overview: MVVM is a design pattern that separates an application into three core components:</p><ol><li><strong>Model:</strong> This component handles the data and business logic of the application. In our scenario, it involves managing data retrieved from the Marvel API.</li><li><strong>View:</strong> This component represents the UI elements and their arrangement. In Flutter, it consists of the widgets that form the user interface.</li><li><strong>ViewModel:</strong> This component serves as a bridge between the Model and the View. It converts the data from the Model into a format that the View can utilize and updates the Model based on user interactions with the View.</li></ol><h3>Let’s start a practical guide</h3><p><strong>Step 1: Setting Up the Project</strong></p><p>Let’s create a new project using this terminal command. You also can create a new project using your IDE.</p><pre>flutter create user_api</pre><p><strong>Step 2: Adding Dependencies</strong></p><p>In our project, we need to incorporate the following dependencies:</p><ol><li><strong>http:</strong> This is a composable, Future-based library used for making HTTP requests. You can find the latest version here.</li><li><strong>provider:</strong> This is a wrapper around InheritedWidget, designed to simplify usage and enhance reusability. The Provider package is frequently employed in Flutter applications for state management and provides a convenient method to propagate changes throughout the widget tree. For more details and the latest version, please check here.</li></ol><p>Open your project in any preferred IDE. I’m using VSCode for my project. Now open the pubspec.yaml file and add the following dependencies:</p><pre>dependencies:<br>  flutter:<br>    sdk: flutter<br><br>  #library for making HTTP requests<br>  http: ^1.2.2<br>  <br>  #library for reuse or init ViewModel<br>  provider: ^6.1.2</pre><p><strong>Step 3: Creating data models for API data</strong></p><p>Create a user_model.dart file to define the structure of the user data:</p><pre>class UserModel {<br>  UserModel({<br>    required this.email,<br>    required this.password,<br>    required this.name,<br>    required this.surname,<br>  });<br><br>  String email;<br>  String password;<br>  String name;<br>  String surname;<br><br>  factory UserModel.fromJson(Map&lt;String, dynamic&gt; json) =&gt; UserModel(<br>        email: json[&quot;email&quot;],<br>        password: json[&quot;password&quot;],<br>        name: json[&quot;name&quot;],<br>        surname: json[&quot;surname&quot;],<br>      );<br><br>  Map&lt;String, dynamic&gt; toJson() =&gt; {<br>        &quot;email&quot;: email,<br>        &quot;password&quot;: password,<br>        &quot;name&quot;: name,<br>        &quot;surname&quot;: surname,<br>      };<br>}</pre><p><strong>Step 4: Create a Service Class</strong></p><p>Now, create a api_service.dart service class to handle the API calls. Service class responsible for making network requests</p><pre>import &#39;dart:convert&#39;;<br><br>import &#39;package:http/http.dart&#39; as http;<br>final class ApiService {<br><br><br>  final String baseUrl = &quot;http://127.0.0.1:3000/api/&quot;; // local<br><br>  Future&lt;http.Response&gt; get(String url) async {<br>    http.Response response = await http.get(Uri.parse(baseUrl +url));<br>    return response;<br>  }<br><br><br>  // post dynamic method<br>  Future&lt;http.Response&gt; post(String url, dynamic data) async {<br>    var response = await http.post(<br>      Uri.parse(baseUrl + url),<br>      body: json.encode(data),<br>      headers: {<br>        &quot;Content-Type&quot;: &quot;application/json&quot;,<br>        &quot;accept&quot;: &quot;application/json&quot;,<br>        &quot;Access-Control-Allow-Origin&quot;: &quot;*&quot;<br>      },<br>    );<br>    return response;<br>  }<br><br><br>}</pre><p><strong>Step 5: Create a Repository Class</strong></p><p>Create a repository.dart repository to abstract the data source.</p><pre><br>import &#39;dart:developer&#39;;<br><br>import &#39;package:http/http.dart&#39;;<br>import &#39;package:user_api/model/user_model.dart&#39;;<br>import &#39;package:user_api/service/api_service.dart&#39;;<br> <br><br>class UserRepository {<br>  static final UserRepository _instance = UserRepository._init();<br>  static UserRepository get instance =&gt; _instance;<br><br>  final ApiService _apiService = ApiService();<br><br>  UserRepository._init();<br>  final String _registerPath = &quot;user/signup&quot;;<br><br>  Future&lt;bool&gt; register(UserModel user) async {<br>    try {<br>      Map data = {<br>        &quot;username&quot;: &quot;${user.name} ${user.surname}&quot;,<br>        &quot;email&quot;: user.email,<br>        &quot;password&quot;: user.password,<br>      };<br><br>      Response response = await _apiService.post(_registerPath, data);<br>      log(response.body);<br>      log(response.statusCode.toString());<br><br>      if (response.statusCode == 200) {<br>        log(&#39;success&#39;);<br>      } else {<br>        print(&#39;error&#39;);<br>      }<br><br>      // status code is 200 so register operation is successful<br>      return response.statusCode == 200;<br>    } catch (e) {<br>      log(e.toString());<br>      // something went error so register operation is not successful<br>      return false;<br>    }<br>  }<br>}<br></pre><p><strong>Step 6: Implementing ViewModel</strong></p><p>Create a user_view_model.dart ViewModel</p><pre>import &#39;package:user_api/model/user_model.dart&#39;;<br>import &#39;package:user_api/service/repository.dart&#39;;<br><br>class UserViewModel extends ChangeNotifier {<br><br>  TextEditingController emailController = TextEditingController();<br>  TextEditingController passwordController = TextEditingController();<br>  TextEditingController nameController = TextEditingController();<br>  TextEditingController surnameController = TextEditingController();<br><br>Future&lt;bool&gt; register() async {<br>    UserModel user = UserModel(<br>      email: emailController.text,<br>      password: passwordController.text,<br>      name: nameController.text,<br>      surname: surnameController.text,<br>    );<br>    bool isRegistered = await UserRepository.instance.register(user);<br>  <br>    return isRegistered;<br>  }<br>}</pre><p><strong>Step 7: Creating the View</strong></p><p>Now, create a user_view.dart file to define the UI.</p><pre>import &#39;dart:convert&#39;;<br>import &#39;dart:developer&#39;;<br><br>import &#39;package:flutter/material.dart&#39;;<br>import &#39;package:flutter_screenutil/flutter_screenutil.dart&#39;;<br>import &#39;package:http/http.dart&#39; as http;<br>import &#39;package:provider/provider.dart&#39;;<br><br>import &#39;package:user_api/user_view_model.dart&#39;;<br>import &#39;package:user_api/widgets/name_field.dart&#39;;<br>import &#39;package:user_api/widgets/surname_field.dart&#39;;<br>import &#39;package:user_api/widgets/email_field.dart&#39;;<br>import &#39;package:user_api/widgets/password_field.dart&#39;;<br>import &#39;../../../../widgets/button/app_button.dart&#39;;<br><br>class RegisterView extends StatefulWidget {<br>  const RegisterView({super.key});<br><br>  @override<br>  State&lt;RegisterView&gt; createState() =&gt; _RegisterViewState();<br>}<br><br>class _RegisterViewState extends State&lt;RegisterView&gt; {<br>  final _formKey = GlobalKey&lt;FormState&gt;();<br><br>  @override<br>  Widget build(BuildContext context) {<br>    final UserViewModel userViewModel = context.watch&lt;UserViewModel&gt;();<br>    return Scaffold(<br>      body: Form(<br>        key: _formKey,<br>        child: Stack(<br>          fit: StackFit.expand,<br>          children: [<br>            Image.asset(<br>              &quot;assets/images/app_bg.png&quot;,<br>            ),<br>            SingleChildScrollView(<br>              child: Column(<br>                children: [<br>                  80.verticalSpace,<br>                  Padding(<br>                    padding: EdgeInsets.symmetric(horizontal: 40.w),<br>                    child: Column(<br>                      children: [<br>                        const NameField(),<br>                        15.verticalSpace,<br>                        const SurnameField(),<br>                        15.verticalSpace,<br>                        EmailField(),<br>                        15.verticalSpace,<br>                        PasswordField(),<br>                        15.verticalSpace,<br>                        AppButtonWidget(<br>                          onPressed: () {<br>                            if (_formKey.currentState!.validate()) {<br>                              userViewModel.register();<br>                            }<br>                          },<br>                          text: &quot;SignUp&quot;,<br>                          color: Colors.red,<br>                          textColor: Colors.white,<br>                        ),<br>                      ],<br>                    ),<br>                  ),<br>                ],<br>              ),<br>            ),<br>          ],<br>        ),<br>      ),<br>    );<br>  }<br>}<br></pre><p>name field widget codes</p><pre><br>class NameField extends StatelessWidget with InputFieldMixin {<br>  const NameField({super.key});<br><br>  @override<br>  Widget build(BuildContext context) {<br>    final UserViewModel userViewModel = context.watch&lt;UserViewModel&gt;();<br>    return TextFormField(<br>      controller: userViewModel.nameController,<br>      decoration: InputDecoration(<br>        hintText: LocaleKeys.registerView_name.tr(),<br>        hintStyle:<br>            AppTextstyles.light16.copyWith(color: AppColors.lightGreyColor),<br>        border: OutlineInputBorder(<br>          borderRadius: BorderRadius.circular(AppBorders.largeBorder),<br>        ),<br>        focusedBorder: OutlineInputBorder(<br>          borderRadius: BorderRadius.circular(AppBorders.largeBorder),<br>        ),<br>        errorBorder: OutlineInputBorder(<br>          borderRadius: BorderRadius.circular(AppBorders.largeBorder),<br>          borderSide: const BorderSide(color: AppColors.redColor),<br>        ),<br>      ),<br>      validator: nameValidator,<br>    );<br>  }<br>}</pre><p><strong>Step 8: Wrap the App with a ChangeNotifierProvider</strong></p><p>Update your main.dart use ChangeNotifierProvider. Replace the content of the main.dart file with the following:</p><pre><br><br>import &#39;package:easy_localization/easy_localization.dart&#39;;<br>import &#39;package:flutter/material.dart&#39;;<br>import &#39;package:flutter_screenutil/flutter_screenutil.dart&#39;;<br><br>import &#39;package:user_api/view_models/user_view_model.dart&#39;;<br>import &#39;package:provider/provider.dart&#39;;<br><br>Future&lt;void&gt; main() async {<br>  await AppInitialize.onAppInit();<br>  runApp(<br>    EasyLocalization(<br>      useOnlyLangCode: true,<br>      fallbackLocale: AppStrings.supportedLocales.first,<br>      path: AppStrings.languagePath,<br>      supportedLocales: AppStrings.supportedLocales,<br>      child: const MyApp(),<br>    ),<br>  );<br>}<br><br>class MyApp extends StatelessWidget {<br>  const MyApp({super.key});<br><br>  @override<br>  Widget build(BuildContext context) {<br>    return MultiProvider(<br>      providers: [<br>        ChangeNotifierProvider(create: (_) =&gt; UserViewModel()),<br><br>      ],<br>      child: ScreenUtilInit(<br>        designSize: const Size(390, 844),<br>        minTextAdapt: true,<br>        splitScreenMode: true,<br>        child: Builder(builder: (_) {<br>          return MaterialApp(<br>            title: AppStrings.appName,<br>            debugShowCheckedModeBanner: false,<br>            localizationsDelegates: context.localizationDelegates,<br>            supportedLocales: context.supportedLocales,<br>            locale: context.locale,<br>            navigatorKey: NavigationService.instance.navigatorKey,<br>            home: const RegisterView(),<br>          );<br>        }),<br>      ),<br>    );<br>  }<br>}</pre><p>That’s it. Finally, run the app using flutter run.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53b69cfd9db1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flutter UI Tips: Using Container, Stack & Position]]></title>
            <link>https://medium.com/@ayseleynavuz/flutter-ui-tips-using-container-stack-position-4cb1f7d274be?source=rss-6a74e9d70941------2</link>
            <guid isPermaLink="false">https://medium.com/p/4cb1f7d274be</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[flutter-ui]]></category>
            <category><![CDATA[flutter-stack-widget]]></category>
            <category><![CDATA[flutter-widget]]></category>
            <category><![CDATA[flutter-clean-code]]></category>
            <dc:creator><![CDATA[Ayseleynavuz]]></dc:creator>
            <pubDate>Sun, 21 Jul 2024 17:28:50 GMT</pubDate>
            <atom:updated>2024-07-21T17:28:50.108Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*fjUEQ7Mzy0LRUutl_cypDQ.png" /></figure><p>Hi, I am currently working on a project as a freelancer where I am designing a page layout that utilizes the stack, position, and container structures together. I decided to write an article on Medium to share the experiences I gained during this process. I hope you like it. Thank you 🙏</p><p>Let’s first take a look at the outermost structure:</p><pre>      Container(<br>            width: 350.w,<br>            height: 85.h,<br>            color: Colors.amber,<br>            child: const Stack(<br>              children: [<br>                // PaymentPlanCard<br>                Center(<br>                  child: PaymentPlanCard(<br>                    paymentTitle: &quot;Weekly payment&quot;,<br>                    textSpan1: &quot;\$4.99&quot;,<br>                    textSpan2: &quot;/per week&quot;,<br>                  ),<br>                ),<br>                // MostPrefferedCard<br>                Positioned(<br>                  left: 20,<br>                  child: MostPrefferedCard(),<br>                ),<br>              ],<br>            ),<br>          ),</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*I9JOWzVY8yFSW6hwsIHJbA.png" /></figure><p>By setting the color of the Container to yellow, we can easily see the area it occupies. The second container structure, which will be placed on top of the first Container, needs some space; therefore, there must be an outermost Container.</p><p>Since these structures will be positioned on top of each other, we are obliged to use a Stack. When using a Stack, the structure given to the bottom row is positioned at the top of the page. Therefore, we have used Position to place the second Container after the first one in the code. Once the design is complete, if the yellow color assigned to the Container is removed and the Container is changed to a SizeBox, everything will be ready.</p><p>Most Preferred Card Design</p><pre>import &#39;package:flutter/material.dart&#39;;<br>import &#39;package:flutter_screenutil/flutter_screenutil.dart&#39;;<br><br>import &#39;../../../core/assets_gen/assets.gen.dart&#39;;<br>import &#39;../../../core/constants/colors/color_constants.dart&#39;;<br>import &#39;../../../core/constants/textStyles/text_style_constants.dart&#39;;<br><br>class MostPrefferedCard extends StatelessWidget {<br>  const MostPrefferedCard({<br>    super.key,<br>  });<br><br>  @override<br>  Widget build(BuildContext context) {<br>    return Container(<br>      height: 26.h,<br>      width: 140.w,<br>      decoration: BoxDecoration(<br>        color: ColorConstants.black,<br>        borderRadius: BorderRadius.all(<br>          Radius.circular(30.r),<br>        ),<br>      ),<br>      child: Row(<br>        mainAxisAlignment: MainAxisAlignment.center,<br>        children: [<br>          Assets.icons.mostPreffered.svg(<br>            height: 17.h,<br>          ),<br>          5.horizontalSpace,<br>          Text(<br>            &quot;Most preferred&quot;,<br>            style: TextStyleConstants.xlightStyle().copyWith(<br>              fontWeight: FontWeight.w600,<br>              color: ColorConstants.white,<br>            ),<br>          ),<br>        ],<br>      ),<br>    );<br>  }<br>}</pre><p>As seen, we create the container design as desired in the layout and extract it as a widget.</p><p>Payment Plan Card — Container</p><pre><br>import &#39;package:flutter/material.dart&#39;;<br>import &#39;package:flutter_screenutil/flutter_screenutil.dart&#39;;<br><br>import &#39;../../../core/constants/colors/color_constants.dart&#39;;<br>import &#39;../../../core/constants/textStyles/text_style_constants.dart&#39;;<br><br>class PaymentPlanCard extends StatelessWidget {<br>  const PaymentPlanCard({<br>    super.key,<br>    this.colorTextSpan1,<br>    this.colorTextSpan2,<br>    this.border,<br>    this.boxColor,<br>    required this.paymentTitle,<br>    this.colorText,<br>    required this.textSpan1,<br>    required this.textSpan2,<br>  });<br><br>  final String paymentTitle;<br>  final String textSpan1;<br>  final String textSpan2;<br>  final Color? colorText;<br>  final Color? colorTextSpan1;<br>  final Color? colorTextSpan2;<br>  final BoxBorder? border;<br>  final Color? boxColor;<br><br>  @override<br>  Widget build(BuildContext context) {<br>    return Container(<br>      width: 335.w,<br>      height: 50.h,<br>      decoration: BoxDecoration(<br>        color: boxColor ?? ColorConstants.primaryColor,<br>        borderRadius: BorderRadius.all(Radius.circular(10.r)),<br>        border: border,<br>      ),<br>      child:<br>          Row(<br>            mainAxisAlignment: MainAxisAlignment.spaceAround,<br>            children: [<br>              Text(<br>                paymentTitle,<br>                style: TextStyleConstants.mediumStyle().copyWith(<br>                  color: colorText ?? ColorConstants.white,<br>                ),<br>              ),<br>              Row(<br>                children: [<br>                  Text.rich(<br>                    TextSpan(<br>                      text: textSpan1,<br>                      style: TextStyleConstants.boldStyle().copyWith(<br>                        color: colorTextSpan1 ?? ColorConstants.white,<br>                      ),<br>                      children: [<br>                        TextSpan(<br>                          text: textSpan2,<br>                          style: TextStyleConstants.mediumStyle().copyWith(<br>                            color: colorTextSpan2 ?? ColorConstants.white,<br>                            fontSize: 12.sp,<br>                          ),<br>                        ),<br>                      ],<br>                    ),<br>                  ),<br>                ],<br>              ),<br>            ],<br>          ),<br>    );<br>  }<br>}<br><br></pre><p>Don’t let the fact that this is a customized container design confuse you. Basically, we create a container and add some decoration to it. We then give the container’s child a row. Inside this row, there’s some text and another row. In the second row, we use the Text.rich structure. This way, we make sure the text elements inside the container look great.</p><p>I think creating designs like this will be much easier from now on! I hope this guide has been helpful for you. If you have any questions or feedback, feel free to reach out. Happy coding! 👩‍💻👨‍💻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cb1f7d274be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Install Node.js on Mac]]></title>
            <link>https://medium.com/@ayseleynavuz/how-to-install-node-js-on-mac-48c641a1437d?source=rss-6a74e9d70941------2</link>
            <guid isPermaLink="false">https://medium.com/p/48c641a1437d</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[zsh-shell]]></category>
            <dc:creator><![CDATA[Ayseleynavuz]]></dc:creator>
            <pubDate>Thu, 11 Jul 2024 14:54:30 GMT</pubDate>
            <atom:updated>2024-07-11T14:54:30.278Z</atom:updated>
            <content:encoded><![CDATA[<h3>MacOS (M1 | M2 | M3)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Sc0N6_W7HF8Ga0yh.jpg" /></figure><p>Node.js is a runtime environment. It is not a programming language or a library. It is an infrastructure that allows JavaScript to run on the backend. Npm is a package management system.</p><ol><li>The pwd command displays the current directory path you are in within the terminal.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GSN_eXsvhBRiLzAP5o2Fxw.png" /></figure><p>You can check all files using the ls -al command. If you do not have a .zshrc file, you will need to create a new one.</p><p>2. Using the touch .zshrc command in the terminal creates a file named .zshrc in the current directory. If this file already exists, the touch command updates the file&#39;s last modified date without altering its content. This file is the configuration file used by the Zsh shell (zsh) and contains commands that are executed when Zsh is started.</p><p>3. To download from GitHub, visit <a href="https://github.com/nvm-sh/nvm">https://github.com/nvm-sh/nvm</a>, navigate to the download section, and copy the highlighted installation command. Then, paste it into your terminal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uykYfDzDujGmlZ1o-rTywQ.png" /></figure><p>4. After pasting the source ~/.zshrc command into the terminal, you will be able to use nvm commands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RD1VTzfj0u2Yb05HaE2Qug.png" /></figure><p>Now you can install the version of Node.js you need. To list all available versions, type nvm ls-remote in the terminal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZcBM_qqAX_nXpYW-qjnDhQ.png" /></figure><h4><strong>For the Curious!</strong></h4><p>When you run the nvm ls-remote command, you get a list of all available Node.js versions that can be managed by NVM (Node Version Manager). This list typically includes version numbers along with some additional labels. Here’s what the labels you see mean:</p><p><strong>LTS (Long Term Support):</strong></p><ul><li><strong>LTS (Gallium, Hydrogen, Iron, etc.):</strong> These labels refer to the Long Term Support (LTS) versions of Node.js. LTS versions receive critical bug fixes and security patches for an extended period. Each LTS version has a code name. For example:</li><li><strong>Gallium:</strong> Node.js 16.x LTS version (became LTS in October 2021).</li><li><strong>Hydrogen:</strong> Node.js 18.x LTS version (became LTS in October 2022).</li><li><strong>Iron:</strong> Node.js 20.x LTS version (became LTS in October 2023).</li></ul><p>LTS versions are preferred for long-term projects due to their stability and extended support.</p><p><strong>Latest:</strong> This label refers to the most recent stable version of Node.js. It includes the latest features and updates with fewer bugs, as the development is completed.</p><p><strong>Current:</strong> This refers to the latest stable version of Node.js available at the moment. It contains the newest features and improvements but has a shorter support period compared to LTS versions.</p><p>5. To install a specific version of Node.js, such as v20.15.1, use the command: nvm install v20.15.1</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VpPAKqnox52yRXVwM8Ljjg.png" /></figure><ul><li>If you want to install another version, simply use the command:</li></ul><pre>nvm install &lt;version-number&gt;</pre><ul><li>To use a specific Node.js version, use the command:</li></ul><pre>nvm use &lt;version-number&gt;</pre><p>And that’s all there is to installing and managing Node.js versions with NVM!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48c641a1437d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Calculator App Auto Layout in Storyboard]]></title>
            <link>https://medium.com/@ayseleynavuz/calculator-app-auto-layout-in-storyboard-31c9d3588e01?source=rss-6a74e9d70941------2</link>
            <guid isPermaLink="false">https://medium.com/p/31c9d3588e01</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[autolayout-constraints]]></category>
            <dc:creator><![CDATA[Ayseleynavuz]]></dc:creator>
            <pubDate>Sat, 20 Apr 2024 14:00:15 GMT</pubDate>
            <atom:updated>2024-04-20T14:00:15.395Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello helloo, while working on the 5th assignment of the iOS Bootcamp program, I noticed that the design was getting distorted when switching to different devices if I didn’t add stack views while making the calculator application. Therefore, I decided to reorganize the project from scratch using auto layout. I’d like to share it with you. In the project, we’ll try to achieve the image at the bottom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*UjMqY9w4WZOYyPBHe_M-yw.png" /></figure><h3>Auto Layout</h3><p>Auto Layout is a system that allows visual objects to be flexibly positioned anywhere on the screen, ensuring a consistent appearance across different devices and screen sizes. It operates using constraints, which provide information about the size and position of a view. For example, constraints can specify that a view should be a certain distance from the top or should expand proportionally with another view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/0*xTDRwp8OLlje6gRL.jpg" /></figure><p><strong>Advantages of Auto Layout :</strong></p><p>Flexibility: Automatically adapts to different screen sizes and devices. Consistency: Ensures that interface elements are always displayed in the same way. Adaptation to Dynamic Changes: Automatically adjusts when screen orientations change or content is dynamically updated. Can be Used with Code or Storyboard.</p><h3><strong>Let’s start our project!</strong></h3><p>First, we create our project and navigate to the storyboard area. I began by setting the background color. I took the Label visual object and placed it at the top of the page, stretching it along the page and setting its text alignment to be on the right. I added a button, customized its background and text color. You can also click on the Custom option in the Color area to add the colors you want in RGB format.</p><p>In the project, I set the background color to (2D2C2D), the button color to orange (F1A33C), text colors to (E8E7E7), the dark gray color for the top three buttons to (414041), and the light gray color to (626162).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b29sZNrd8NUCs6yiPtyREQ.png" /></figure><p>Then, I added a button and placed four of them side by side. I copied the four buttons placed side by side and added them in five rows below each other. Then, I arranged their texts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*DG-wLHUWbGlmqJAM56O-CA.png" /></figure><p>After these steps, I obtain an image like this. Then, we select the buttons arranged horizontally and add them one by one to a stack view. We do this to ensure that we achieve the same appearance on the screen even if the device sizes change. Then, we add all of them, including the label, to a separate stack view. After that, we set the constraints to 0 from all sides in the outermost stack view, and the “constraints to margin” option will not be checked.</p><p>The outermost stack’s settings should be as follows:</p><blockquote><em>From the settings, select secondItem = Superview.Top and set constant = 0</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*WgWZJ8K1n416Crr_.jpeg" /></figure><p>Then, we arrange each stack view individually:</p><p>-&gt; Set Alignment to Fill, Distribution to Fill Equally, and Spacing value to 1 for all inner stack views.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BtAxSi6-LjUISu4M_scRHA.png" /></figure><p>Once these steps are completed, adjustments are made for the outermost stack view. Select Alignment as Fill, Distribution as Fill Equally, and Spacing as 1. It looks like the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*z3U-YthxKHwxu9JE8mAvdA.png" /></figure><p>Then, at the bottom row where there are (0) (.) (=) buttons, since the space occupied by (0) will be larger according to the design, we create a separate stack for (.) and (=) buttons. We select Alignment as Fill, Distribution as Fill Equally, and Spacing as 1 for this stack as well.</p><p>For the label, we apply the following constraint:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*jjYouoKdKc5LBLOYwBWlTg.png" /></figure><p>Now we can run our application for iPhone 11 and see how it looks. If we run it for other devices as well, the layout will appear consistently without distortion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/1*EVkD8kZ1Tq6uzG_o_Qnfhg.png" /></figure><p>In the design, the label area seemed small to me, so I placed the areas outside the label into a separate stack. I selected Alignment as Fill, Distribution as Fill Equally, and Spacing as 1 for this stack from the settings. Instead of the label, I wrote 0, and this is the image I obtained.</p><p>The final file view will look like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ie5vAnWkS3p3Oo6nUmoMuw.png" /></figure><p>The design section is complete. Now, it’s time for coding!</p><p>Resources:</p><p>[1] <a href="https://mrfu.me/2017/09/05/AutoLayout_for_a_Calculator/">https://mrfu.me/2017/09/05/AutoLayout_for_a_Calculator/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31c9d3588e01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pushing Your Xcode Project to GitHub: A Step-by-Step Guide]]></title>
            <link>https://medium.com/@ayseleynavuz/pushing-your-xcode-project-to-github-a-step-by-step-guide-8d424ece9495?source=rss-6a74e9d70941------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d424ece9495</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Ayseleynavuz]]></dc:creator>
            <pubDate>Sat, 13 Apr 2024 13:14:04 GMT</pubDate>
            <atom:updated>2024-04-13T13:14:04.890Z</atom:updated>
            <content:encoded><![CDATA[<p>Establishing a Github Connection with xCode — Push and Commit Your Files</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x6IJtZ_RO35zBvZc.jpeg" /></figure><p>Hey there! 🚀, As part of the <a href="https://www.udemy.com/course/ios-bootcamp-program-swift/?couponCode=KEEPLEARNING">Kasım Adalan iOS Bootcamp</a> program on Udemy, I will explain how to establish a connection between Xcode and GitHub, and how to push code changes.</p><p>Ready to get started? Let’s dive in! 🛠️💻</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*tSHB-4qJf75a5Pp9.jpeg" /><figcaption>image (<a href="https://dev.to/kirekov/spring-boot-testing-data-and-services-288f">https://dev.to/kirekov/spring-boot-testing-data-and-services-288f</a>)</figcaption></figure><p>First, navigate to the GitHub <strong>settings.</strong> Click on “<strong>Developer settings</strong>” located at the bottom, and from there, select “<strong>Generate new token</strong>” under the “<strong>Classic</strong>” options. How to Create a New GitHub Access Token:</p><ol><li>You can quickly access it from this address: <a href="https://github.com/settings/tokens/new">https://github.com/settings/tokens/new</a></li><li>Choose the expiration date for your token. To avoid frequent renewals, I prefer to use <strong>“no expiration”</strong></li><li>The permissions necessary for Xcode integration are now accessible. These permissions are crucial for managing and accessing repositories. Therefore, it’s recommended to select at least the “<strong>repo”</strong> and <strong>“repo:status”</strong> permissions. Thus, ensure that your GitHub token has these two permissions at minimum for Xcode integration</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0rmR6PpxT5OqhgIjXVKTMg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7H3bdQGQxaA7bitQ-HAfxw.png" /></figure><p>After you’ve chosen the desired scopes, proceed by clicking on the <strong>“Generate token” </strong>button located at the bottom of the page.</p><p>GitHub will generate a new access token for you. Be sure to copy and securely store this token, as it will be hidden from view once you leave the page.</p><p>Congratulations! You have successfully generated a GitHub access token. Now, let’s proceed to configure Xcode with this token.</p><h4>Setting Up Xcode with the GitHub Access Token</h4><p>To configure Xcode with your GitHub Access Token, start by launching Xcode and navigating to the Preferences window. You can access this window by clicking on Xcode in the menu bar and selecting Settings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*OP1q5Y_lQSJI5FoP83HfcQ.png" /></figure><p>To add your GitHub account, click the <strong>“+”</strong> button at the bottom left corner of the Accounts tab. A dialog box will appear with a list of available account types. Select <strong>GitHub</strong> from the list and click on the <strong>Continue</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R_LEefYPFPHRL7bOwaTQnA.png" /></figure><p>Copy and paste the previously generated access token here, and then proceed with signing in</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u9JRW96xGqoIZtMSIsE1rg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ylZ8LfaHMoUzDPFcvJyhqA.png" /></figure><p>Authorized, you’ll return to Xcode’s Accounts tab, where your GitHub account should be listed.</p><p>Congrats! Xcode’s now set up with your GitHub access token. Utilize Xcode’s version control features to commit and push changes to your GitHub repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PTO3xB31n4jYsVZvX181og.png" /></figure><p>(*.DS_Store) files are typically found on macOS operating systems and store folder arrangements. They are not uploaded to GitHub because they can create unnecessary noise among project files and are generally meaningless for shared projects. You can ensure they are not uploaded to GitHub by adding them to the .gitignore file.</p><p>Later, we create a new repository by selecting ‘Create a new repository’. I named it ios-bootcamp.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*6OvFGus_SmW6JgQrQ5B97g.png" /></figure><p>Afterwards, select the ‘Create a new repository’ option to create a new repository. I named it ‘ios-bootcamp’. Then, navigate to Xcode and choose new git repository</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cZTHjOWR-iPPNBdEFP8-6A.png" /></figure><p>As seen, the repository has been created. Here, you navigate to the remote section and click on add existing remote</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*C1R4tFQuKByMHit0_UJ-Gg.png" /></figure><p>When creating a GitHub repository, we copy the link that appears.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bwk4QFSFhARb77l2_sPmRw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*5J1vCfA1ulPns4ROV8u_eQ.png" /></figure><p>Then, you push the changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*geTUFjyTJfkL9VtOyzY8sQ.png" /></figure><p>And that’s it, you’ve connected your project to GitHub.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T7HOIkBfVVAOjZaCPHZ-bA.png" /></figure><p>Thank you for reading this far. I’m aware it’s been quite a lengthy read, but I wanted to explain in detail. I hope you found it helpful. Take care of yourself :))</p><p>Resources:</p><ol><li><a href="https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens">https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens</a></li><li><a href="https://developer.apple.com/documentation/xcode/configuring-source-control-preferences-in-xcode">https://developer.apple.com/documentation/xcode/configuring-source-control-preferences-in-xcode</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d424ece9495" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>