<?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 Batuhan Saka on Medium]]></title>
        <description><![CDATA[Stories by Batuhan Saka on Medium]]></description>
        <link>https://medium.com/@batuhans?source=rss-a611145b777b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ooGAny3AcHYR0r26XoE5xQ.jpeg</url>
            <title>Stories by Batuhan Saka on Medium</title>
            <link>https://medium.com/@batuhans?source=rss-a611145b777b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:20:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@batuhans/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[Revamping Trendyol’s iOS App: A Modularization Success Story]]></title>
            <link>https://medium.com/trendyol-tech/revamping-trendyols-ios-app-a-modularization-success-story-a6c1d2c4188b?source=rss-a611145b777b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6c1d2c4188b</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[scalability]]></category>
            <category><![CDATA[modularization]]></category>
            <dc:creator><![CDATA[Batuhan Saka]]></dc:creator>
            <pubDate>Mon, 06 Mar 2023 15:42:14 GMT</pubDate>
            <atom:updated>2023-03-06T15:42:14.486Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NuRuUvArrQNLPFfP" /><figcaption>Photo by <a href="https://unsplash.com/@colinextremis?utm_source=medium&amp;utm_medium=referral">Coline Beulin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If you’re not familiar with Trendyol, it’s one of Turkey’s leading e-commerce platforms, offering a wide range of products from fashion to home decor. But Trendyol is more than just an online retailer — it’s a <strong>super-app</strong> that brings together several omnichannel services, including meal ordering, grocery ordering, international shopping across Europe, and second-hand marketplaces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UbxPaE5UZdaElKJ5veIGuA.jpeg" /><figcaption>Trendyol Super App (Turkey core commerce, International core commerce, Second-hand, Meal, Grocery)</figcaption></figure><p>Behind the scenes, our talented team of developers is working hard to keep the platform running smoothly and efficiently. In recent years, we have embarked on an <strong>ambitious journey</strong> towards <strong>modularization</strong>, with the goal of improving <strong>developer experience</strong>, <strong>scalability</strong>, and <strong>build times</strong>. In this article, we’ll dive into the progress we have made, and the lessons we’ve learned along the way.</p><p>At the start of 2020, we were far from a monolithic iOS application. With over 170 modules in our codebase, we struggled to navigate the challenges of circular dependencies, dependency hell, and build settings management. By fueling the problems we tried to avoid with the solutions we made, we caused it to grow. Despite our best efforts, these issues slowed down our development process and caused frustration for our team. However, we were determined to find a better way forward.</p><p>You can see the changes we have made in the Trendyol app over the years in the timeline below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VfFlWNgBqdHsiK1YjsK3Rg.png" /><figcaption>Trendyol iOS app modularization timeline</figcaption></figure><p>Even back then, we were aware that in order to align with the direction our application was taking, we needed to move away from a monolithic structure and towards a more modular approach. However, the rapid growth of the project, combined with certain practices we had adopted and the business needs we were trying to meet, brought forth a set of distinct challenges.</p><p>Let’s talk about the improvements we have made in sections below and the steps we have taken.</p><h3>Attempt to migrate from CocoaPods to SPM</h3><p>Until 2021, we were using <strong>CocoaPods</strong> as our package manager to include third-party packages in our project. <strong>CocoaPods</strong> directly integrated with our Xcode project and brought along its own targets and schemas. It also stored the downloaded third-party frameworks’ resources in a folder called “<strong>Pods</strong>” in the project directory.</p><p>We were sending the <strong>Pods</strong> folder to the remote repository, which was significantly increasing the repository size and negatively affecting the Git history. Additionally, since <strong>CocoaPods</strong> was a black box, we sometimes had to spend hours to resolve frustrating build issues.</p><p>So we decided to try Apple’s newly announced <strong>SPM</strong> and integrated it as a POC. We successfully replaced all the third-party packages from <strong>CocoaPods</strong> to <strong>SPM</strong>. However, when we tried to include our internal feature and helper modules with <strong>SPM</strong>, we faced resolving issues that significantly affected the developer experience. We saw that there were a few discussions about this issue on Apple’s forums as well. Therefore, we had to give up on this option.</p><h3>Xcode at scale</h3><p>One of the main issues was the difficulty in managing a growing number of <strong>.xcodeproj</strong> files, which in turn led to a decrease in consistency between build configurations.</p><p>For example, we noticed that due to manually setting build configurations for all <strong>Xcode projects</strong> and not using a tool to keep them in sync, we had left the <strong>optimization level</strong> at <strong>-Onone</strong> in a few projects. This resulted in <strong>increased application size</strong>. <a href="https://developer.apple.com/documentation/xcode/doing-basic-optimization-to-reduce-your-app-s-size#Check-your-targets-build-settings-for-release-builds">Learn more.</a></p><p>Additionally, conflicts between <strong>.xcodeproj</strong> and <strong>.xcworkspace</strong> files can be frustrating and error-prone when working on a <strong>monorepo</strong> with a <strong>large team</strong>.</p><p>As a result of all these issues, <strong>Tuist</strong> became our <strong>savior</strong>. In the following section, you can see how we benefited from it and how it helped us improve our processes.</p><h3>Tuist migration</h3><p>Tuist automates the generation of your <strong>Xcode projects</strong> and <strong>workspaces</strong> with the specified configurations, ensuring maximum consistency. It simplifies <strong>managing configurations</strong> across projects and helps you avoid drowning in the hundreds of interfaces available in Xcode. <a href="https://docs.tuist.io/tutorial/get-started">Learn more.</a></p><p>In fact, you can even <strong>create templates</strong> specific to your project and <strong>create a new module</strong> in less than a second with a <strong>single CLI command</strong>. <a href="https://docs.tuist.io/commands/scaffold/">Learn more.</a></p><p><strong>What have we started doing after Tuist migration?</strong></p><ul><li>Eliminated the need for committing Xcode project and workspace files to version control by generating them at runtime, reducing the risk of merge conflicts and enabling greater flexibility in managing project files</li><li>Ensured consistency across projects by eliminating manual configuration of Xcode projects</li><li>Reduced the complexity of managing Xcode projects and workspaces by simplifying configuration with Tuist</li><li>Improved productivity by reducing the time required for setting up new modules with the help of Tuist templates</li><li>Improved the overall developer experience by reducing the number of manual steps required for project configuration and setup.</li><li>Utilizing Tuist’s graph command to visualize and analyze the dependency graph of our project, allowing us to better understand the relationships between modules and identify potential issues or optimizations.</li></ul><h3>Third Party Dependencies as XCFrameworks</h3><p>Before <strong>Tuist migration</strong>, we were using <strong>CocoaPods</strong> and linking <strong>170+ internal frameworks</strong> in our application dynamically. This resulted in <strong>compiling third-party code repeatedly</strong>, leading to a <strong>larger application size</strong> and <strong>longer pre-main time</strong>.</p><p>After migrating to <strong>Tuist</strong>, we converted these frameworks into <strong>XCFrameworks</strong> and linked them to our application <strong>statically</strong>. Additionally, we serve these <strong>third-party XCFrameworks</strong> ourselves, version them, and include them in the project with <strong>a central SPM project</strong>.</p><p>This allowed us to include them at <strong>compile time</strong>, avoiding these issues and resulting in <strong>faster compilation</strong>, <strong>smaller application size</strong>, and <strong>less pre-main time</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*6Yr5QNQ4pxhSsxsTPoIS0Q.png" /><figcaption>Static vs Dynamic Linking comparison</figcaption></figure><p>As you can see in the table, using <strong>dynamic frameworks</strong> increases your <strong>pre-main time</strong> and also negatively <strong>affects your application size</strong>. However, it should be noted that <strong>static frameworks</strong> have some drawbacks along with their benefits. You need to do <strong>bundle matching</strong> and <strong>resource management</strong> yourself.</p><h3>Using Interface Modules</h3><p>Partitioning your application into modules may enhance the build times. However, in the absence of comprehensive understanding regarding the organization of your <strong>dependency graph</strong>, even a single line of code change can significantly impact your <strong>incremental build times</strong>, leading to a <strong>poorer developer experience</strong>.</p><p>If you were developing a small application, you would likely build a <strong>monolithic</strong> structure and <strong>keep all code and resources under the AppTarget</strong>. This is not a problem as long as the scale of your application is small. However, in larger applications like <strong>Trendyol</strong> with <strong>hundreds of modules</strong>, even the smallest change you make can <strong>cause the entire app to be recompiled</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/1*qQb-MqIpPEb9QnqyK1-Muw.png" /><figcaption>Monolith application (code and resources bundled into same target)</figcaption></figure><p>Assuming you have decided to modularize your application and separated its screens/features into their own modules, you would end up with a structure similar to the following.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XhhbpmYeV5JYPH6ZZuHDBw.png" /><figcaption>Modular application (each feature modules’ code and resources bundled itself)</figcaption></figure><p>At first glance, everything may seem fine, but as the number of screens increases, these feature modules will need to add other modules as dependencies, and we will end up with a dependency graph like the one below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*37Z9mVsxRlZTb3qxY52J6Q.png" /><figcaption>Modular application (Concrete modules adds each other as dependencies)</figcaption></figure><p>Since concrete modules have added each other as dependencies, we will face the same problem here as we did in the monolithic application. Because any change made to the those modules will cause all modules to be recompiled.</p><p>Therefore, we decided to use <strong>Interface Modules</strong>. In this approach, each module has its own Interface target. As far as I know, <strong>Spotify</strong> and <strong>some companies</strong> prefer to create an <strong>extra Xcode project</strong> to store Interfaces in the target of that project, instead of adding Interface targets to concrete modules. However, we chose this method because we want to <strong>keep the number of modules down</strong> and we believe that it is <strong>more organized</strong>. In this target, we only use primitive types and models necessary to initialize the modules, and we make sure not to add other modules as dependencies.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/654585e424798d38374bec2d2c87a968/href">https://medium.com/media/654585e424798d38374bec2d2c87a968/href</a></iframe><p>By having an initialization class and an interface for each module, we are able to keep the access modifiers of the classes that can be accessed from outside the module as internal. This means that only the classes that we explicitly mark as public in the interface are visible outside the module. This allows us to better control the module’s public API and ensure that the implementation details remain hidden from external modules, providing better encapsulation and reducing the risk of unintended coupling between modules.</p><p>Once you have separated your modules into concrete and interface targets, you need to register their implementations and public APIs at runtime through your dependency container structure.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e6fd7bce05344b091cb011dd298db5f6/href">https://medium.com/media/e6fd7bce05344b091cb011dd298db5f6/href</a></iframe><p>Afterwards, during runtime, you should access and use the modules through interfaces via your dependency container structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BCdZ4Rn-G1QiafVkrhUXQg.png" /><figcaption>Modular application (separated Public API and Impl targets)</figcaption></figure><p>As seen, <strong>no concrete module</strong> is now dependent on <strong>another concrete module</strong>. They communicate with each other directly through the <strong>Public API</strong>. Thus, we ensure that <strong>only the places we make changes to are compiled</strong>.</p><p>It should be noted that as concrete modules become more dependent on each other, Xcode’s build process becomes more bottlenecked. This is because with <strong>vertical dependency graphs</strong>, dependencies are built one by one and we cannot take advantage of <strong>parallel building</strong>. Therefore, if we pay attention to creating <strong>horizontal dependency graphs</strong>, we can inevitably achieve <strong>better build times</strong>.</p><p>When we started this journey, we did not have a dedicated team at Trendyol that specifically focused on these issues. In response to these needs, we established a <strong>Platform team</strong> and began conducting <strong>research</strong> and <strong>work</strong> with a <strong>Developer Experience focus</strong>. In order to provide a basis for comparison, I would like to share a few comparisons related to our <strong>build times</strong>, <strong>pre-main time</strong>, and <strong>application size</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fwmhwdCdZkKSq5NU1PLtIA.png" /><figcaption>Trendyol iOS App Performance Metrics comparison</figcaption></figure><p>Please note that the old metrics provided several years ago were based on an earlier stage of our improvements, and since then, <strong>numerous features</strong> have been added and <strong>multiple frameworks</strong> have been integrated into <strong>Trendyol iOS application</strong>.</p><p>Additionally, we can say that the size of Trendyol’s iOS team working on the application has grown <strong>fivefold</strong> in the <strong>last 2 years</strong>.</p><h4>TL;DR</h4><p>Trendyol migrated its iOS project to <strong>Tuist</strong> to <strong>improve developer experience</strong> and <strong>build efficiency</strong>, resulting in <strong>reduced build times</strong>, <strong>smaller app size</strong>, and <strong>better dependency management</strong>. The creation of a dedicated iOS Platform team enabled focused <strong>research</strong> and <strong>development</strong>, leading to <strong>significant improvements in the platform’s metrics</strong>.</p><h4>More Info</h4><p>If you’re interested in improving modularization and performance metrics, you can check out a few resources we benefited from:</p><ul><li>A great presentation by Bruno Rocha — <a href="https://www.youtube.com/watch?v=sZuI6z8qSmc">Preparing for Growth: Architecting Giant Apps for Scalability and Build Speed</a></li><li><a href="https://bpoplauschi.github.io/2021/10/25/Advanced-static-vs-dynamic-libraries-and-frameworks.html">Advanced Static vs Dynamic libraries and frameworks on iOS (and macOS)</a></li></ul><h4>Want to work in this team?</h4><p>Do you want to join us on the journey of building the e-commerce platform that has the most positive impact?</p><p><a href="https://jobs.lever.co/trendyol?lever-via=owTdoLt7AX">Have a look at the roles we’re looking for!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6c1d2c4188b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trendyol-tech/revamping-trendyols-ios-app-a-modularization-success-story-a6c1d2c4188b">Revamping Trendyol’s iOS App: A Modularization Success Story</a> was originally published in <a href="https://medium.com/trendyol-tech">Trendyol Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Securing iOS Applications with SSL Pinning]]></title>
            <link>https://medium.com/trendyol-tech/securing-ios-applications-with-ssl-pinning-38d551945306?source=rss-a611145b777b------2</link>
            <guid isPermaLink="false">https://medium.com/p/38d551945306</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[ssl]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Batuhan Saka]]></dc:creator>
            <pubDate>Mon, 18 Jan 2021 08:40:14 GMT</pubDate>
            <atom:updated>2023-06-26T08:20:51.708Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yfH_5h1V8ujBp-bF" /><figcaption>Photo by <a href="https://unsplash.com/@calina?utm_source=medium&amp;utm_medium=referral">Georg Bommeli</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>What is SSL?</h4><blockquote><strong>Secure Sockets Layer (SSL)</strong> is cryptographic protocol designed to provide communications security over a computer network. Several versions of the protocols are widely used in applications such as email, instant messaging, and voice over IP, but its use as the Security layer in HTTPS remains the most publicly visible.</blockquote><h4>What is SSL Pinning?</h4><p><strong>Secure Socket Layer (SSL) </strong>Pinning is the process of associating a host with its certificate or public key.</p><h4>Why Should I Use SSL Pinning?</h4><p>Using <strong>Secure Socket Layer (SSL)</strong> Pinning allows you to protect your apps against the many types of Man-in-the-middle (<a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack"><strong>MITM</strong></a>) attacks and interception of its network traffic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CfP9BsShy-2t26MR.png" /></figure><h4>What types of SSL pinning methods are there?</h4><ol><li><strong>Embedding the Certificate:</strong> You can extract the server’s certificate and embed into your app bundle. The network layer compares the server’s certificate with embedded certificate.</li><li><strong>Embedding the Public Key: </strong>You can extract the certificate’s public key and define into your code or place into the app bundle. The network layer compares the servers certificates’ public key with embedded one.</li></ol><h4>What’s Difference Using The Root, Leaf and Intermediate Certificates In Pinning?</h4><p><strong>Leaf Certificate: </strong>If the certificate becomes invalid because of expiration or a compromising, the application will be broken until you update SSL certificate.</p><p><strong>Intermediate Certificate: </strong>As long as your certificate provider is the same, any changes to the leaf certificate will not require an update in your application.</p><p><strong>Root Certificate: </strong>The root certificate comes from the trusted certificate authority. Pinning the root certificate puts trust in the root cert authority, as well as all intermediaries that the root cert authority trusts.</p><p><strong>Note: </strong>The all mentioned types can be pinned on your application. But, only pinning the root certificate puts your application in the risk because of its scope.</p><h4><strong>How should you embed the Certificate into App Bundle?</strong></h4><p>First, the certificate file must be encoded before the embed into the app bundle. You can ensure whether the file is encoded by opening your certificate file with a text editor. <strong>If you see similar content like Base64 output, it means the content of the certificate must be encoded.</strong></p><ul><li>You can encode the certificate with proper format by importing the existing certificate file into the keychain and extracting back. The given output will be encoded as default.</li><li>If you do not have any certificate file to the embed into app bundle. You can retrieve the certificate with ready to use format by running the command below.</li></ul><pre>openssl s_client -connect &lt;hostname&gt;:443 &lt;/dev/null \<br> | openssl x509 -outform DER -out &lt;certificatename&gt;.der</pre><h4>Is it possible to pin the certificate without embedding into the App Bundle?</h4><p>The extracting the bundle files from the IPA is quite easy. If you have concerns to put the certificate into there, you may avoid this.</p><ul><li>You can place the Base64 format of the certificate into your codebase and convert into the <a href="https://developer.apple.com/documentation/security/seccertificate">SecCertificate</a> during the runtime. The Base64 format of the certificate can be obtained by running the following command below.</li></ul><pre>base64 &lt;certificatename&gt;.der</pre><h4><strong>How to implement the SSL Pinning on iOS?</strong></h4><p>There are two common approach in that matter.</p><ul><li>If you use <a href="https://github.com/Alamofire/Alamofire">Alamofire</a> which is the most popular network library in iOS, that allows you to pin the certificate or public keys by using the provided default trust evaluators with ease. (PinnedCertificatesTrustEvaluator &amp; PublicKeysTrustEvaluator)</li></ul><p>PinnedCertificatesTrustEvaluator expects certificates as parameter to initialize the evaluator. It is provided by Alamofire as <a href="https://github.com/Alamofire/Alamofire/blob/eaf6e622dd41b07b251d8f01752eab31bc811493/Source/ServerTrustEvaluation.swift#L215">default</a>. If you want to specify by yourself, you may override the provided default value with your own SecCertificate array.</p><p>All you need is to set up the Session instance by using a ServerTrustManager with provided trust evaluators.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/431fca6e12f52b762413769177bcc180/href">https://medium.com/media/431fca6e12f52b762413769177bcc180/href</a></iframe><p>You can figure out the full details about the trust evaluators on the <a href="https://github.com/Alamofire/Alamofire/blob/master/Documentation/AdvancedUsage.md#security">Alamofire documentation</a>.</p><ul><li>You can use the <strong>Apple API’s</strong> to pin the certificate or public keys through the <a href="https://developer.apple.com/documentation/foundation/urlsession">URLSession</a>.</li></ul><p>As you know, Apple is providing the URLSession which enables us to perform network tasks. To achieve the same outcome via <strong>Apple API’s</strong>, you should initiate an URLSession instance with proper configuration and manage the SSL handshake process through the <a href="https://developer.apple.com/documentation/foundation/urlsessiondelegate">URLSessionDelegate</a>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/816a26da97a98e44a01d65f5a692f1b8/href">https://medium.com/media/816a26da97a98e44a01d65f5a692f1b8/href</a></iframe><p>Furthermore, the host validation mechanism can be added by accessing through the challenge.protectionSpace.host in the same block to enhance the security too. You may pin the several certificates and map these certificates with any host.</p><h4>Thanks for reading! 🚀</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38d551945306" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trendyol-tech/securing-ios-applications-with-ssl-pinning-38d551945306">Securing iOS Applications with SSL Pinning</a> was originally published in <a href="https://medium.com/trendyol-tech">Trendyol Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WWDC 2018: I Built a Game in a Day and Got Flown to California]]></title>
            <link>https://batuhans.medium.com/the-incredible-week-wwdc18-771fe584f22a?source=rss-a611145b777b------2</link>
            <guid isPermaLink="false">https://medium.com/p/771fe584f22a</guid>
            <category><![CDATA[san-francisco]]></category>
            <category><![CDATA[scholarship]]></category>
            <category><![CDATA[san-jose]]></category>
            <category><![CDATA[wwdc]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Batuhan Saka]]></dc:creator>
            <pubDate>Fri, 15 Jun 2018 03:32:59 GMT</pubDate>
            <atom:updated>2026-05-16T15:28:47.487Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hvresue3XgqXkPLlUWZigg.png" /><figcaption>San Jose McEnery Convention Center — taken by me</figcaption></figure><p>I’m not sure anything quite prepares you for the moment you board a plane knowing you’re heading to WWDC. As a scholarship recipient, it felt like a milestone I’d worked toward without fully believing it would happen. By the time I reached the gate, the excitement had taken over completely.</p><p>In this post I want to share what the week was actually like: the travel, the sessions, the people I met, the food worth eating, getting around California, the Bash, and a bit about my scholarship submission. Whether you’re hoping to attend one day or just curious what it’s like, I hope this gives you a real sense of it.</p><h4>Getting There</h4><p>After landing in San Francisco and clearing the airport, I took an Uber down to San Jose and settled into a dormitory at <strong>San Jose State University </strong>— a convenient, affordable option for scholars that keeps you close to the <strong>McEnery Convention Center</strong>. On the first morning, I headed to Apple’s check-in desk to collect my scholarship package: a WWDC 2018 badge, the jacket, a set of pins (the Turkish flag pin was my personal favourite), and a pair of AirPods.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9o3x7WNw434RUbNp.JPG" /><figcaption>San Jose State University</figcaption></figure><h4>The Sessions</h4><p>The week was a mix of sessions, labs, and conversations. I attended around a dozen sessions over the conference:</p><ul><li><a href="https://developer.apple.com/videos/play/wwdc2018/229/">Using Collections Effectively</a></li><li><a href="https://developer.apple.com/videos/play/wwdc2015/106/">What’s New in Swift</a></li><li><a href="https://developer.apple.com/videos/play/wwdc2018/803/">Designing Fluid Interfaces</a></li><li><a href="https://developer.apple.com/videos/play/wwdc2018/806/">Designing Notifications</a></li><li><a href="https://developer.apple.com/videos/play/wwdc2018/802/">Intentional Design</a></li><li><a href="https://developer.apple.com/videos/play/wwdc2017/409/">What’s New in Testing</a> 1</li><li><a href="https://developer.apple.com/videos/play/wwdc2018/403/">What’s New in Testing</a> 2</li><li><a href="https://developer.apple.com/videos/play/wwdc2014/232/">Advanced User Interfaces with Collection Views</a></li><li><a href="https://developer.apple.com/videos/play/wwdc2018/406/">Swift Generics</a></li><li><a href="https://developer.apple.com/videos/play/wwdc2017/212/">What’s New in Foundation</a></li><li><a href="https://developer.apple.com/videos/play/wwdc2018/412/">Advanced Debugging with Xcode and LLDB</a></li><li><a href="https://developer.apple.com/videos/play/wwdc2016/407/">Auditing Your Apps for Accessibility</a></li></ul><p>other sessions can be accessed from <a href="https://developer.apple.com/videos/">here</a>.</p><p>Don’t skip the design sessions — they’re packed with practical techniques and details you won’t find in the documentation. On the Swift side, the language took some meaningful steps forward this year and the sessions did a solid job of making those changes concrete.</p><h4>The People</h4><p>This was the part I didn’t expect. Apple engineers were everywhere — at labs, in hallways, at meals — and the atmosphere was far more open and approachable than I’d imagined. You could walk up and have a real conversation. I met scholars from all over the world, each with their own story.</p><h4>Food Worth Knowing About</h4><p>California has no shortage of great food, and San Jose is no exception. Here’s what I’d recommend:</p><p><strong>In-N-Out Burger </strong>—Affordable, fast, and genuinely good. We went on the first day and it didn’t disappoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/0*eiG-Zv8iY0bonugc" /></figure><p><strong>Johnny Rockets </strong>— A bit pricier, but worth trying. I’d still give the edge to In-N-Out, but it’s a solid option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/0*HccyMVa2LsIZ2xwt.jpg" /></figure><p><strong>Pizza My Heart </strong>— Great pizza by the slice. Exactly what you want after a long day of sessions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*hWcH7U7Z2j7VMtqM" /></figure><p>Apple’s donuts and fresh juices at the conference itself were also a nice touch — simple but appreciated.</p><h4>Getting Around California</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*T_iyWCNqrUswRavf" /></figure><p>For everyday transport,</p><p><strong>Uber </strong>and <strong>Lyft </strong>are reliable and easy to use throughout the Bay Area. For short trips,</p><p><strong>Bird </strong>and <strong>Lime </strong>electric scooters were a fun way to get around. I rode Bird scooters to the convention center on the first morning. <strong>Ford GoBike </strong>is also available if you’d rather cycle.</p><h4>The Bash</h4><p>The closing celebration was held at Discovery Meadow, with <strong>Panic! At the Disco </strong>headlining. It was a great concert and a fitting end to an intense week.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*rS8K4NEgUpXrbU6K.jpg" /><figcaption>Panic! at the Disco is on the stage</figcaption></figure><h4>The Submission</h4><p>I’ll be honest: I built my scholarship playground in a single day. It was a game using <strong>SpriteKit</strong>, <strong>UIKit</strong>, and <strong>AVFoundation</strong>, and I was deliberate about the code quality despite the tight timeline — focusing on protocol-oriented programming, clean use of extensions and closures, and keeping the codebase readable. For the essay, I wrote about what I’d built, what I’d learned, and where I wanted to go next. I think sincerity matters there more than trying to sound impressive.</p><h4>Final Thoughts</h4><p>WWDC 2018 was one of those weeks that’s hard to summarise. The sessions were valuable, but what stayed with me most was the community — developers from all over the world, at every stage of their careers, all building things they genuinely cared about. That’s not something you get from watching the videos online. If you’re thinking about applying for a scholarship, do it. And if you get in — make the most of every moment.</p><p><strong>WWDC 2018</strong> was held <strong>June 4–8</strong> in <strong>San Jose, California</strong>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fopen.spotify.com%2Fembed%2Fplaylist%2F6SuIaSq4UNtcRIYsHiJPqT&amp;display_name=Spotify&amp;url=https%3A%2F%2Fopen.spotify.com%2Fplaylist%2F6SuIaSq4UNtcRIYsHiJPqT&amp;image=https%3A%2F%2Fi.scdn.co%2Fimage%2Fab67706c0000bebb96b608ac85d3c23082b0bbfb&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=spotify" width="300" height="380" frameborder="0" scrolling="no"><a href="https://medium.com/media/098d1f4f49c5e75f2ff6a22891563a8c/href">https://medium.com/media/098d1f4f49c5e75f2ff6a22891563a8c/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*CIx0Ow7PMvY67TjJacQ3EA@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=771fe584f22a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>