<?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 Chayce Heiberg on Medium]]></title>
        <description><![CDATA[Stories by Chayce Heiberg on Medium]]></description>
        <link>https://medium.com/@chayceheiberg?source=rss-5aa062c327cf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LULG11eN9hpECBh96ciTaQ.jpeg</url>
            <title>Stories by Chayce Heiberg on Medium</title>
            <link>https://medium.com/@chayceheiberg?source=rss-5aa062c327cf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 21:49:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chayceheiberg/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[Why I Write My Views Programmatically (And Not In A StoryBoard)]]></title>
            <link>https://medium.com/@chayceheiberg/why-i-write-my-views-programmatically-and-not-in-a-storyboard-313dfd35baea?source=rss-5aa062c327cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/313dfd35baea</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Chayce Heiberg]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 16:57:53 GMT</pubDate>
            <atom:updated>2017-10-12T21:50:17.231Z</atom:updated>
            <content:encoded><![CDATA[<p>For the majority of people, storyboards are introduced at an early stage of learning iOS development. Most tutorials and videos reference view controllers and view objects from the storyboard because of the ease of dragging an object onto the screen, and developers can depend on that object appearing on the screen at run-time. For many projects that beginners work through, storyboards make the development process quick and simple. This is the case for most apps that are aren’t dynamic in nature because the developer knows where each UI component will be placed on the screen, and its size will remain static.</p><p>What happens when a user clicks a button that is supposed the shrink a view or transition new view components? You could designate an action and outlet to the view object, but changing the constraints across multiple user interactions can cause trouble if the constraints were initialized by ctrl-dragging to anchor points. Most of the time, new developers aren’t keeping track of the constraints for each view object because the constraints aren’t explicitly labeled in code, but rather hidden in the xml file of the storyboard or represented by the blue lines that are a pain to hover over when there are several view objects on the screen. To make the UI development process faster and more organized, I write my views in code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*abBFJ_J-APM-wCpDNcD33w.png" /></figure><p>At first it might look like a lot of unnecessary code that could be replaced with storyboard objects, but programmatic views are documented in the code itself. If the developer needs to change the title of a button, instead of going to the storyboard, finding the correct editor tab, and then scrolling down until they find the title editor, they can find the view container code block and quickly reference the setTitle() method. This saves time on the amount of clicks, and it may not seem like such a big deal, but when working on an app with several dozen views, locating the correct view object will be a lot more efficient than searching through storyboards. Another advantage is that the constraints of a view object can be referenced when written in code so that developers can ensure the object isn’t abnormally sized at run-time when a button size needs to increase or be repositioned on the screen.</p><p>Like most things, writing views in code takes practice to get efficient at, but in the end it will save you valuable time in the development lifecycle, and give you a much deeper understanding of the UIKit framework. For any iOS developer looking to build a more complex and dynamic app, programmatic views can give you a major advantage in delivering a scalable and beautiful mobile application.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=313dfd35baea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[iOS Programming: How to Mimic Tinder Card Animations]]></title>
            <link>https://medium.com/@chayceheiberg/ios-programming-how-to-mimic-tinder-card-animations-e5916a6ba3ea?source=rss-5aa062c327cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5916a6ba3ea</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[tinder]]></category>
            <dc:creator><![CDATA[Chayce Heiberg]]></dc:creator>
            <pubDate>Fri, 08 Sep 2017 20:44:28 GMT</pubDate>
            <atom:updated>2017-09-08T20:45:18.633Z</atom:updated>
            <content:encoded><![CDATA[<p>Keeping users engaged is a vital part of having and maintaining a successful mobile application. Designing a simple and clean UI helps developers achieve such success with their app, and hopefully keeps users from double tapping the home button and swiping up to kill your app.</p><p>When developing my first app, my approach was to first layout a foundation for the UI. What did I want my app to look like, and how did I want users to interact with the features that I provided? I began by looking at existing apps that had thousands of downloads and wanted to implement some of their features into my own. My first app allowed users to create flashcards in order to study off of. In order to traverse flashcards in an efficient manner, I began researching Tinder and how they were able to achieve the swipe ability of subviews.</p><p>Building dynamic animations for subviews from scratch is a daunting task, especially for a beginner like me at the time. Instead of writing my own framework, I found an open source framework designed by Yalantis called Koloda. This framework is very similar to UITableView, where there is a defined interface for dataSource and delegate methods. Using Koloda, I was able to build the foundation for my UI rapidly since the framework allowed me to load my custom NIB file that mimicked a flashcard that users could edit or save.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IPhwYTIYT6m_dJXeOGp-9g.png" /></figure><p>For more information about installing Koloda and how to customize the swipe animations, you can visit their <a href="https://github.com/Yalantis/Koloda">repository on Github</a>.</p><p>To check out my flashcard app called Plorio you can find it on the Appstore, or see how I built it by visiting <a href="https://github.com/Chaycej/Plorio">my repository.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5916a6ba3ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>