<?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 Chase Roossin on Medium]]></title>
        <description><![CDATA[Stories by Chase Roossin on Medium]]></description>
        <link>https://medium.com/@croo?source=rss-5d1819d222e9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kbJu6u8rWr3IA2riVIunZA.jpeg</url>
            <title>Stories by Chase Roossin on Medium</title>
            <link>https://medium.com/@croo?source=rss-5d1819d222e9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:19:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@croo/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[Tackling latency, availability, and security with AWS’s CloudFront and Certificate Manager]]></title>
            <link>https://medium.com/@croo/tackling-latency-availability-and-security-with-awss-cloudfront-and-certificate-manager-c28cfb697a3?source=rss-5d1819d222e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/c28cfb697a3</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[acm]]></category>
            <category><![CDATA[latency]]></category>
            <category><![CDATA[ssl]]></category>
            <category><![CDATA[cloudfront]]></category>
            <dc:creator><![CDATA[Chase Roossin]]></dc:creator>
            <pubDate>Wed, 29 May 2019 03:34:40 GMT</pubDate>
            <atom:updated>2019-05-29T03:34:40.387Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*_gB8VKx1aQF8VEAbS6lQVQ.png" /><figcaption>AWS CloudFront — AWS Certificate Manager</figcaption></figure><p>In my <a href="https://hackernoon.com/using-gitlab-ci-cd-to-auto-deploy-your-vue-js-application-to-aws-s3-9affe1eb3457">previous post</a>, I discussed how one could use GitLab’s pipelines to enable continuous delivery of your web-app to Amazon’s S3 buckets. However, this is only the first step to achieving a production-ready environment. You want to keep your web-app secure, right? What about delivering it to your users with low-latency and high availability? That’s where CloudFront and Certificate Manager (ACM) come into play.</p><p>Let’s review: We have a web-app deployed to an S3 bucket that has web-hosting enabled, but we have no sort of CDN or cloud caching and certainly, no security (SSL certificates). Your application flow may look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*fOBRoTCWfRlev0Aiqd0lBQ.png" /><figcaption>The user is in direct communication with S3 bucket</figcaption></figure><p>This means that all requests coming from your users are going to directly access that S3 bucket, regardless of geolocation or amount of requests it is receiving; that is obviously not efficient and not necessarily secure. Enter <a href="https://aws.amazon.com/cloudfront/">CloudFront</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*HNUkcAifP4pQkD1M_ZMDAA.png" /><figcaption>CloudFront Edge Locations</figcaption></figure><p>As you can see in the image above, CloudFront has the idea of a “global network”.</p><blockquote>Amazon CloudFront uses a global network of 166 Points of Presence (155 Edge Locations and 11 Regional Edge Caches) in 65 cities across 29 countries.</blockquote><p>In essence, the way that this works and achieves efficiency is by having the DNS route traffic through CloudFront, which determines the best Edge Location that can serve the request — generally the closest location in terms of latency. Each Edge Location internally determines if it has the desired file in its cache. If it has a cached copy of the requested file it will return it, else it will go fetch it from the connected S3 bucket, cache it, and then return it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*DajjGgpJLwAw16fmMBmrgg.png" /><figcaption>A request coming to a CloudFront Edge Location</figcaption></figure><p>(1) A user pings your website</p><p>(2) A request is made to the nearest Edge Location</p><p>(3) If file is cached, return to user</p><p>(3a) If file is not cached, fetch from Amazon S3 bucket</p><p>(3b) Return file from S3 and store in Edge Location</p><p>(3c) Return file to user</p><p>Now that we have a good grip on how CloudFront works, let’s start implementing it. First things first, we will need to create our SSL certificate with ACM that we can consume when setting up our CloudFront Distribution.</p><p>Head over to <a href="https://console.aws.amazon.com/acm/home?region=us-east-1#/">ACM</a> and <strong>ensure</strong> that you are in US-East-1 (N. Virginia) region. For some reason, only certificates issued from this region are accepted by CloudFront.</p><p>Click the “Request a certificate” in the upper left-hand corner and then choose “Request a public certificate” on the following page. Enter the domain that you want to secure like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*FLEYj5NN0wojIE_AsKL8vg.png" /><figcaption>You can use a wildcard (*) to ensure the SSL certificate is valid for all subdomains</figcaption></figure><p>The next step is verification. You may choose either email or DNS validation. Either is acceptable, and you may choose whichever is best suited for your situation. After the verification process has been completed, you should see an “Issued” certificate in your ACM dashboard.</p><p>Back to CloudFront!</p><p>Navigate to your CloudFront dashboard and click “<a href="https://console.aws.amazon.com/cloudfront/home?#create-distribution:">Create Distribution</a>”. Do not worry about the region, since CloudFront is by definition “everywhere” 😊.</p><p>Now we need to configure CloudFront’s properties. When you click on the “Origin Domain Name” text-field you should see a drop-down of your S3 buckets; go ahead and select the S3 bucket you want to have CloudFront manage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RpIxc5VUVIPFRphIbhEqqQ.png" /></figure><p>Additionally, insert the following configurations:</p><ol><li><strong>Viewer Protocol Policy</strong>: “Redirect HTTP to HTTPS”</li><li><strong>Object Caching</strong>: You may put “0” during development stages so that it always fetches and your changes are immediately reflected. However, you will normally want to set a default TTL (time-to-live) that CloudFront will adhere to.</li><li><strong>SSL Certificate</strong>: Select “Custom SSL Certificate” and then choose the one you created in the previous step. We want to be secure! 🔒</li><li><strong>Default Root Object</strong>: index.html</li></ol><p>Lastly, click “Create Distribution” and wait for it to deploy!</p><p><em>Note: You may change your </em><strong><em>Price Class</em></strong><em> when configuring your CloudFront distribution. Obviously, this should be determined by your use case. If you have users who are located all over the world, using all edge locations would be the most performant; however, it would cost more than just US or Canada.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FDffShiJ47fPqM%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FDffShiJ47fPqM%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FDffShiJ47fPqM%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="290" frameborder="0" scrolling="no"><a href="https://medium.com/media/e92b75a1454d3a24dda41a5266ee1936/href">https://medium.com/media/e92b75a1454d3a24dda41a5266ee1936/href</a></iframe><p>We are all set! Your app is not only secured, but it is highly available with blazing fast latency! Remember, don’t forget to check out <a href="https://hackernoon.com/using-gitlab-ci-cd-to-auto-deploy-your-vue-js-application-to-aws-s3-9affe1eb3457">part 1</a> if you would like to see how to deploy your web-app to S3.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c28cfb697a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using GitLab CI/CD to auto-deploy your Vue.js application to AWS S3]]></title>
            <link>https://medium.com/hackernoon/using-gitlab-ci-cd-to-auto-deploy-your-vue-js-application-to-aws-s3-9affe1eb3457?source=rss-5d1819d222e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/9affe1eb3457</guid>
            <category><![CDATA[hackernoon-top-story]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[gitlab]]></category>
            <dc:creator><![CDATA[Chase Roossin]]></dc:creator>
            <pubDate>Tue, 26 Feb 2019 19:48:44 GMT</pubDate>
            <atom:updated>2019-03-08T03:19:22.808Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iKzGFY_QP1l3fsP2jY9Zgg.png" /><figcaption>GitLab CI/CD — Vue.js — Amazon S3</figcaption></figure><p>In my previous years as an engineer, I always looked at Continuous Integration/Continuous Delivery (CI/CD) with a smug face. It has never been anything but a rough experience (thank you, Jenkins 🤢). However, it is my firm belief that in 2019 we will be seeing an uptick in conversation about how to easily manage and deploy your apps; considering developing the app is only a single step, right?</p><p><em>For this article, I am going to assume that you have already created a </em><a href="https://vuejs.org/"><em>Vue.js</em></a><em> application and are now ready to set up with GitLab’s continuous deployment.</em></p><p><em>Although this article shows how to deploy a Vue.js app, it is the basic structure for using GitLab’s CI/CD to deploy anything to S3.</em></p><p>First things first, let’s set up an <a href="https://aws.amazon.com/">AWS account</a> and create a new S3 bucket! Any new AWS accounts go under their <a href="https://aws.amazon.com/free/">free tier</a> which will allow us to deploy to S3 for free (for the first year, under certain request constraints).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*s_9MRei-XuERuFWMFDivuQ.jpeg" /></figure><p><strong>S3:</strong></p><p>Once signed up, head over to the <a href="https://s3.console.aws.amazon.com/s3/home">S3 console</a> and click “Create Bucket”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kI0_ocJEShO1h3zCnz56Uw.png" /><figcaption>Create bucket modal</figcaption></figure><p>You will be shown this modal. Enter in a bucket name (remember this will be required to be unique across AWS). On the “Set Permissions” tab, ensure you uncheck “Block new public bucket policies” and “Block public and cross-account access if bucket has public policies”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r_X_98tFojhYuvBrt3mlsA.png" /></figure><p>After the bucket has been created, click into the bucket and click the second tab called “Properties”. You will see a card called “Static website hosting”. Click that and enable “use this bucket to host a website” and fill in index.html for the index document as so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WGWKJ4zRVK3IjtE5xELi3A.png" /></figure><p><em>Note: The endpoint at the top of the modal will be the URL you can use to access your website!</em></p><p>Now for the final part, allow read permissions to your S3 bucket (so your users can see your awesome website!). Navigate to the third tab that says “Permissions” and then click “Bucket Policy”. You will need to add the following policy in the editor:</p><pre>{<br>    &quot;Version&quot;: &quot;2012-10-17&quot;,<br>    &quot;Statement&quot;: [<br>        {<br>            &quot;Effect&quot;: &quot;Allow&quot;, <br>            &quot;Principal&quot;: &quot;*&quot;, <br>            &quot;Action&quot;: &quot;s3:GetObject&quot;, <br>            &quot;Resource&quot;: &quot;arn:aws:s3:::YOUR_BUCKET_NAME/*&quot; <br>        } <br>    ] <br>}</pre><p><em>Don’t forget to replace </em><em>YOUR_BUCKET_NAME with the bucket name that you used when creating. This allows any user to </em><em>GET from your bucket.</em></p><p>Head back over to the “Public Access Settings” tab and re-enable blocking new bucket policies:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*N8TtJlmxg6FeQwfbA5dICQ.png" /><figcaption>This ensures the bucket policy cannot be updated</figcaption></figure><p>Now if we go to the URL that Amazon assigned this bucket, you should see a… 404! That’s because we haven’t pushed your project from GitLab!</p><p>The final thing we must do in the AWS dashboard is to create an IAM user so that we can safely allow GitLab to access and upload data to this bucket. This allows us to revoke access if we ever need to.</p><p><strong>IAM User:</strong></p><p>Navigate to the <a href="https://console.aws.amazon.com/iam/home?#/users">IAM Management Console</a> and click the blue “Add user” button at the top. Give a descriptive username such as gitlabci and select “Programmatic access”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/1*9CMGWnnPcDKxb530jDxFfA.png" /></figure><p>You will next create a group if you haven’t already done so and attach a policy. For the means of this demo, we will use AmazonS3FullAccess — however, you may want to change policies based on your security needs.</p><p>After the final step when you click “create user” you will be shown a success screen, which will house two very important pieces of information: Access Key and Secret Key. <strong>Note:</strong> <strong>Once you leave this screen, you will no longer have access to the Secret Key</strong>. You can either write it down or download the .csv and then <strong>ensure</strong> you delete later. Whatever you do, make certain that no one gains access to the keys.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*JRMz3vZUyIOK872yo_Y5Rg.png" /><figcaption>Either download the .csv or click show secret key and copy and paste somewhere</figcaption></figure><p>We’re almost there! Now we just need to setup GitLab to push to our S3 bucket.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FR2m2NzVxQ3pbG%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Freactiongifs-R2m2NzVxQ3pbG&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FR2m2NzVxQ3pbG%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="185" frameborder="0" scrolling="no"><a href="https://medium.com/media/fdaf6ad5a62358a9aef1bad0a8cf89a4/href">https://medium.com/media/fdaf6ad5a62358a9aef1bad0a8cf89a4/href</a></iframe><p><strong>GitLab:</strong></p><p>Welcome, GitLab CI/CD. Prior to testing out <a href="https://docs.gitlab.com/ee/ci/">GitLab CI/CD</a> I always hosted my code on GitHub. GitHub did an amazing job at keeping my source code secure and widely available, however, I noticed that without some elbow grease, it did pretty much just that. I told myself that I wanted to be able to make a code change, commit, push, and then see my new code deployed on the internet.</p><p>Head over to <a href="https://gitlab.com/">GitLab</a>, signup for an account, and create a new project. GitLab acts just as GitHub in the sense that you will need to add its remote origin to your local project. Once the project is setup you will rename/add this as a new remote to your local .git :</p><pre>git remote rename origin old-origin<br>git remote add origin https://gitlab.com/croossin/vues3example.git<br>git push -u origin --all</pre><p>Now for the key file that you need in order to get CI/CD setup with GitLab:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/097fb6fe7bd6b7ae739842097885d817/href">https://medium.com/media/097fb6fe7bd6b7ae739842097885d817/href</a></iframe><p>Go to the root directory of your app and add this file .gitlab-ci.yml and copy the content of the above Gist; once pushed, GitLab will automatically recognize and begin it’s “dev-ops” process.</p><p>So what exactly does this file do?</p><pre>stages:  <br>   - build  <br>   - deploy</pre><p>This tells GitLab what “steps” to run during your CI/CD process. You can easily forsee adding more steps such as test, etc. Let’s take a look at the first stage — <strong>build</strong>:</p><pre>build prod:  <br>   image: node:10.15.0-stretch  <br>   stage: build  <br>   only:    <br>      - tags  <br>   script:    <br>      # Install vuecli    <br>      - npm install -g @vue/cli@latest    <br>      # Install dependencies    <br>      - npm install    <br>      # Build App    <br>      - npm run build  <br>   artifacts:    <br>      paths:      <br>         # Build folder      <br>         - dist/    <br>      expire_in: 1 hour</pre><ul><li><strong>image</strong>: Since we are building our Vue.js app, we will want to set the docker image to be some version (preferably latest) of Node.</li><li><strong>stage</strong>: This should coincide with one of the stages that we described at the very top of the file. This let’s GitLab know how stages are associated.</li><li><strong>only</strong>: This is very key if you want GitLab to run these scripts conditionally based on a specific branch or tag. For me, I like to set up a stage and production environment. When I merge changes into master, it will run the stage scripts, and when I create a tag, it will run the prod scripts.</li><li><strong>script</strong>: As it may sound, this is sequence of commands that are run in this stage. For this particular instance, we install the latest <a href="https://cli.vuejs.org/">Vue Cli</a>, download all the dependencies, and then run our build script from our package.json — which for me looks something like: vue-cli-service build</li><li><strong>artifacts</strong>: <em>Now this is what got me tripped up in the beginning.</em> Since we have two stages in our deployment process (build and deploy) and they are both on two different images, we need a way for the second stage (deploy) to have access to our build folder — dist/ . With artifacts, we can set a path to “store” for other stages to reference. Thus, I set my path for the dist/ folder and set an expiration for 1 hour.</li></ul><p>Now for the final stage in the pipeline — <strong>deploy</strong>:</p><pre>deploy prod:  <br>   image: python:latest  <br>   stage: deploy  <br>   only:    <br>      - tags  <br>   script:    <br>      - pip install awscli    <br>      - aws s3 sync ./dist s3://YOUR_BUCKET_NAME</pre><p>Python is the supported CLI for AWS, so we set our image to python:latest. When this runs, it will install the latest AWS CLI and sync the dist folder with the bucket we created in the beginning. Ensure YOUR_BUCKET_NAME is the same as the bucket we created in the S3 console.</p><p><em>Note: If you want both stage and production environments, you will need to create a second bucket in S3 (with the same configuration as the first) and use that as the staging bucket.</em></p><p><strong>Last Step:</strong></p><p>How does AWS know that it should allow this user to sync to the S3 bucket? From the IAM user we created in the beginning half of the article! Since I mentioned that it is an extremely bad technique to expose/commit your keys we will add them to GitLab’s <a href="https://docs.gitlab.com/ee/ci/variables/">environment variables</a>. Navigate to the CI/CD in the Settings tab and expand “Environment Variables”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_GyyUU3jo56VP24zNpbvtw.png" /><figcaption>GitLab AWS Environment Variables</figcaption></figure><p>You will add two variables: AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY . Fill in the values with the associated keys that you downloaded/copied when created the user in the IAM management console.</p><p>We’re all set to test it out!</p><p>Push some code to master and watch GitLab automatically kick off the CI/CD process. You can watch the stages execute and see your completed pipelines:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/1*soWHLiPImGU57hBMv3-4cQ.png" /></figure><p>Take a look at <a href="https://docs.gitlab.com/ee/ci/README.html">GitLabs CI/CD documentation</a> to see how you can extend your jobs to accomplish anything you may need.</p><p><strong>Summed up:</strong></p><p>After completing these steps, you should in essence have:</p><ul><li>Created an AWS account</li><li>Created an S3 bucket and set permissions to public access</li><li>Created an IAM user for GitLab to use</li><li>Create a GitLab account/project</li><li>Add our .gitlab-ci.yml and fill with our CI/CD stages</li><li>Add our IAM credentials as environment variables</li><li>Sit back, smile, and watch as your code is automatically deployed to S3 via GitLab’s CI/CD process</li></ul><p>Feel free to comment, clap, or reach out if you have any questions or concern. I am planning to write a follow-up article in which I will show you how to deploy a <a href="https://aws.amazon.com/cloudfront/">CloudFront</a> distribution in front of your S3 bucket to ensure fast and reliable distribution of your site as well as adding SSL certs from AWS’s <a href="https://aws.amazon.com/certificate-manager/">Certificate Manager</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9affe1eb3457" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/using-gitlab-ci-cd-to-auto-deploy-your-vue-js-application-to-aws-s3-9affe1eb3457">Using GitLab CI/CD to auto-deploy your Vue.js application to AWS S3</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rebuilding Mint’s UI From the Ground Up Using CardParts (iOS)]]></title>
            <link>https://medium.com/intuit-engineering/rebuilding-mints-ui-from-the-ground-up-using-cardparts-ios-817aac6c863f?source=rss-5d1819d222e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/817aac6c863f</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Chase Roossin]]></dc:creator>
            <pubDate>Wed, 03 Oct 2018 17:41:21 GMT</pubDate>
            <atom:updated>2018-10-03T17:41:21.001Z</atom:updated>
            <content:encoded><![CDATA[<p>Written and edited by <a href="https://medium.com/u/b566664c73cf">Deniz Tumer</a> &amp; <a href="https://medium.com/u/5d1819d222e9">Chase Roossin</a></p><p>It’s impossible! Too ambitious! Overhauling the user interface of Mint — a multi-feature iOS application that has not changed significantly since it’s launch in 2008 — seems like a daunting endeavor. How was our development team able to accomplish this redesign? Easy. We used a UI framework we built called <a href="https://github.com/intuit/CardParts">CardParts</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-sTYX2VXweHYQ5JpXCYSeg@2x.jpeg" /></figure><h3>What is CardParts?</h3><p>CardParts is a reactive, card-based UI framework built on top of Apple’s UIKit framework. CardParts brings the MVVM (Model-View-ViewModel) design paradigm to life and allows developers to focus on building a functional and interactive UI rather than reinventing the wheel every time they need to build a new UI.</p><blockquote>“…great use of POP to separate out display traits, and 💯 for view controller containment.” — <a href="https://twitter.com/twostraws/status/1013711249404780544">Paul Hudson, Hacking with Swift</a></blockquote><p>The primary intent of CardParts is to provide a UI architecture that is easy to build with and even easier to test. Developers can apply protocol-driven traits to their cards and leverage the MVVM design paradigm to shift complex logic away from view controllers and into view models. Creating this view controller containment allows for the view model logic to be tested easily and separately from view controllers.</p><h3>What Did We Do?</h3><p>Now that we had a UI framework that could allow our engineering team to move fast we set out to revamp the Mint user experience. We settled on a design that focused on surfacing cards to users that will help them gain more insight into their personal finances. Of course we call these insight cards MintSights.</p><p>To achieve this goal of revamping the customer experience we leveraged everything that CardParts has to offer. We employed a MVVM architecture, and utilized custom traits to fully customize the user experience and provide a wide variety of features in MintSights. Let’s walk through our process for the MintSight card.</p><p>The MintSight card is a colorful and uniform card that grabs the user’s attention. Each card contains similar design elements — an icon, title, and description. We were able to create a generic view controller and view model to support this functionality and create a reactive UI. The following are examples of the view controller and view model code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c72933e3cf3bd185332140855b8b00be/href">https://medium.com/media/c72933e3cf3bd185332140855b8b00be/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/730730a5c8d9653c5372a6421a7ffd5e/href">https://medium.com/media/730730a5c8d9653c5372a6421a7ffd5e/href</a></iframe><p>CardParts utilizes the power of <a href="https://github.com/ReactiveX/RxSwift">RxSwift</a> to create reactive UIs — binding data from our view models to view controllers. This allows for any changes in the view model data to be reflected immediately in the UI! All that is left is to setup a listener that enabled changes in the internal <a href="https://realm.io/docs/swift/latest/">Realm</a> persistence database to be reflected in the UI. Here is an example of how we accomplished that:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/706d6c617581e41ef39d0745addbcf00/href">https://medium.com/media/706d6c617581e41ef39d0745addbcf00/href</a></iframe><p>And it was as easy as that! Leveraging CardParts enabled us to create a minimum viable product in just a few days. We were able to spend more time adding complex feature that would provide users with insight into their personal finances.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FTXJiSN8vCERuE%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fcartoons-comics-excited-humor-TXJiSN8vCERuE&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FTXJiSN8vCERuE%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="234" frameborder="0" scrolling="no"><a href="https://medium.com/media/9cb30c56a312280ac90a0a0914de0f03/href">https://medium.com/media/9cb30c56a312280ac90a0a0914de0f03/href</a></iframe><h4>What we learned</h4><p>With <a href="https://github.com/intuit/CardParts">CardParts</a> we are easily and quickly able to stub out our card-based designs and keep our UI layer up-to-date with every change that came back from the server. The architectural flow went roughly as follows:</p><ol><li>Network Response</li><li>Persist in Realm</li><li>viewModel notified via Realm notification block</li><li>Apply logic on cached data returned from notification block</li><li>Change reactive variables in viewModel</li><li>UI updates due to be being bound to aforementioned reactive variables</li></ol><p>Our ViewController practically consists only of UI setup such as fonts, colors, margins, etc. while our viewModels do all the heavy lifting of data manipulation — thus we can easily test these viewModels and ensure they are acting as desired.</p><h4>Final Thoughts</h4><p>CardParts has enabled us to move faster than ever before. A feature that might have taken weeks in the past now only takes a few days. We can focus on building algorithms and complex logic to provide the best user experience possible rather than building boilerplate code for every custom UI in the application.</p><p>We just recently open-sourced CardParts to allow everyone to leverage its benefits. Visit our <a href="https://github.com/intuit/CardParts">GitHub page</a> and help us make CardParts one of the most powerful card-based UI frameworks out there! We hope that CardParts can also help you rebuild your application’s UI in just three weeks!</p><h4><strong>Shoutout to the Mint iOS Engineering Team</strong></h4><ul><li><a href="https://www.linkedin.com/in/bharath-urs-908aa946/">Bharath Urs</a></li><li><a href="https://www.linkedin.com/in/peter-fong-12460a97/">Peter Fong</a></li><li><a href="https://www.linkedin.com/in/dtumer/">Deniz Tumer</a></li><li><a href="https://www.linkedin.com/in/chaseroossin/">Chase Roossin</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=817aac6c863f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/intuit-engineering/rebuilding-mints-ui-from-the-ground-up-using-cardparts-ios-817aac6c863f">Rebuilding Mint’s UI From the Ground Up Using CardParts (iOS)</a> was originally published in <a href="https://medium.com/intuit-engineering">Intuit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>