<?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 Chloe Lee on Medium]]></title>
        <description><![CDATA[Stories by Chloe Lee on Medium]]></description>
        <link>https://medium.com/@chaemin2001?source=rss-43e26c27c766------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZYm2mOWnp9MIj-NYdUNmPw.jpeg</url>
            <title>Stories by Chloe Lee on Medium</title>
            <link>https://medium.com/@chaemin2001?source=rss-43e26c27c766------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:27:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chaemin2001/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[How to Perfect a Side Project]]></title>
            <link>https://medium.com/@chaemin2001/how-to-perfect-a-side-project-7bd372484672?source=rss-43e26c27c766------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bd372484672</guid>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[mobile-computing]]></category>
            <dc:creator><![CDATA[Chloe Lee]]></dc:creator>
            <pubDate>Wed, 06 Sep 2023 05:00:21 GMT</pubDate>
            <atom:updated>2023-09-06T05:00:21.463Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Perfect a Side Project: Take a look at my app from a 15-week side project</h3><p>It’s always exciting to come up with an idea, but the process of verifying it through market research and narrowing down the target user pool is challenging. Especially for designers or developers like us.</p><p>Besides, are there any guarantee that the logical building based on your sole investigation is perfect? When you work on your own, you might be thinking in a biased way, filtering out evidences that do not match your conclusion.</p><p><strong>So I encourage iOS developers to build their ideas into a running App first, and then update the released App.</strong> This comes with a lot of advantages, for instance, it becomes much easier to conduct user tests. There would be several users who happen to download your app, and you can get feedbacks from them. Or by analyzing their usage patterns, you can collect useful information that would help you expand the service further.</p><p>As such, it is very common for developers and designers to team up and launch apps as side projects with minimal market research. If you look at the top paid apps on App Store, you can see that most are quite easy-to-create apps, such as Diary or To Do List.</p><p><strong>Based on these insights, I decided to create an app within a 15 week long side project. Our team consists of three people, two developers and one designer, including me, and we had meetings four hours a week.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CC0hrd53vM59SZOorR7AWA.png" /></figure><p><strong>Our app “GodBaby’s GodLife” is an app that helps users choose a habit and keep it.</strong></p><p>In this article, I would like to share my story of how I perfected my first side project. For any project, <strong>idea, team members, and work process</strong> are the most important factor. Let me tell you my experience and thoughts on these three things.</p><p>I came up with our app idea from “GodLife”, a newly coined term popular among the Korean MZ generation. It is “God-saeng” in Korean, a combination of two words “God” and “Life”. It roughly means a very good life. There are various interpretations of GodLife, but it is most often used to call a lifestyle of a typical hardworking and flawless person, like someone who works out every day, eats healthy, studies hard, and never has bad hair day.</p><p><strong>To put all of this together, I guess the contextual meaning of “GodLife” is “A desirable lifestyle in which time, energy, and money are spent on oneself.”</strong> I don’t think that “GodLife” comes from a fragment of life, but rather from habits and attitudes toward life that can be practiced every day. My biggest question was then why most people won’t think of their own everyday lives as “GodLife”.</p><p>One reason may be that it is hard to relate one’s daily habits and routines to their future self. So it might not be so encouraging to choose their own routine or habit and to keep it. Or in other cases, people tend to be discouraged when they fail to complete their routine for just one day. They feel as if they failed the whole challenge. In fact, I was also disappointed with myself for forgetting my routine for a day or two, and stopped using the routine app afterwards.</p><p><strong>So I came up with a solution “Let’s help users look back on one’s lifestyle routine by experiencing other people’s habits”. It was a rough plan for the app called “GodBaby’s GodLife”.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*XOeEOVWoowkXv_uH-97Qyg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*cFd0qzI_l2dz8h13qZ9WWA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*1wipJa3WbgsR5jbQnaiDPw.png" /><figcaption>Onboarding View</figcaption></figure><p>“GodBaby”, or “Gotgi” in Korean is a combination of words ‘God’ and ‘Baby’, which means a very capable and successful young person. It is famous as Jang Won-young’s nickname, a Korean idol. <strong>Through this app name, I wanted to let users know that they should stop blaming themselves and rather think of themselves as babies.</strong> You may not be able to follow your routine for a day or two, but since you are still in your developing stage, it would be meaningful to experience other people’s lifestyles.</p><p>I went around talking about this idea, and was able to find a few who got interested. It then became much easier for me to offer them to do a side project with me on this.</p><p>Since it was my original idea, I found myself most responsible for this project. So I was able to keep the team working without losing interest until the end. Besides, since most of our solutions were fixed beforehand, we were able to build and service the app without major conflicts.</p><p><strong>I figured out the team for this side project pretty fast, by asking several among the people who showed interest in my idea.</strong> One of the most important criteria for finding teammates was whether I have worked with them or not. It is always hard getting used to someone’s working pattern or communication style. So, I guessed it would be more easy if we were already teammates, which both of them were.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a4l1GBAeAh7BL16MBPXFUw.png" /><figcaption>Initial Technology Stack</figcaption></figure><p>In addition, we were a perfect match since we all had our goals, such as studying Django for me, and making portfolio for our designer. The division of work was very clear, three people each responsible for design, frontend, and backend.</p><p>Especially, the other developer had a good understanding of SwiftUI and UIKit through a number of side projects and academy team projects. Also, since we were a member of the server study together, I thought it would be a good opportunity to discuss the parts that I was stuck in. Our designer had special talent in creating an emotional and cute app. Also, her smart and context-understanding communication skills stood out.</p><p>We got together for two hours to discuss “Godsaeng” project before our main project meeting. We all agreed that it was a much lighter and happier project than our main project.</p><p>For the work process, we divided it by weeks. <strong>During the first week, we went through the app planning to see if we had the same picture in mind.</strong> We made a list of essential app features and collected ideas for app contents. Through this, we were able to guess the app size and the work needed, and I was able to determine the app concept and values we could deliver.</p><p>From the second week to the fourth week we worked on design, drawing Lo-Fi and Hi-Fi prototype of the app. <strong>Design is mostly about predicting and guiding user behavior.</strong> So rather than leaving all the task to the designer alone, we first explained to each other of how we pictured the app in mind. We drew various kinds of user flow and tried to make the design as intuitive as possible. Since we developers participated in the design process, we were able to sort out reusable views and understand the reasoning behind each User Interface.</p><p>In particular, at the branding stage, I presented most of ideas for our app concept. I delivered my opinion on what users should feel and experience about the baby concept and how the overall atmosphere should be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vWY3jeZawl4nBNakt3nikQ.png" /><figcaption>Character Sketch</figcaption></figure><p>The rest of the process was easy because all we had to do was to focus on one’s development task. Our meetings were mainly about sharing progress and overall feedback to each other. At final stage, we actively used online chatting and zoom meetings to fix bugs.</p><p>This was a brief summary of my side-project. I’m open to new projects, especially ones that include data collection from wearable devices or model optimization. I’ll be back with something new soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bd372484672" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starting Django as a Total Beginner]]></title>
            <link>https://medium.com/@chaemin2001/starting-django-as-a-total-beginner-21c3b1a8109f?source=rss-43e26c27c766------2</link>
            <guid isPermaLink="false">https://medium.com/p/21c3b1a8109f</guid>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[full-stack-developer]]></category>
            <category><![CDATA[django]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Chloe Lee]]></dc:creator>
            <pubDate>Sun, 29 Jan 2023 11:28:38 GMT</pubDate>
            <atom:updated>2023-01-29T11:28:38.480Z</atom:updated>
            <content:encoded><![CDATA[<h3>Starting Django as a Total Beginner: But finally got our app server running</h3><p>When it comes to coming up with app ideas and bringing it to reality, server is needed in most cases. Although I was a total beginner, I was able to work on a backend team for our app ‘Relay’.</p><p>I chose <strong>Django</strong> as a backend stack, and started working on it. For database, I chose <strong>Postgresql</strong>. If I can do it, you can also! Finish your own django project in a month by following my steps as a total beginner.</p><h4>Step 1: Draw a Database ERD for your project</h4><p>Try drawing a database ERD for your project. It doesn’t have to be perfect. You can edit it anytime later, but still it gives you much sense of how you should structure out your database. Here is a sample of one of my first ERD for our app ‘Relay’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A35HgAivA7YhyKw244UL9Q.png" /></figure><p>Here is a link to refer to understand ERD.</p><p><a href="https://www.visual-paradigm.com/guide/data-modeling/what-is-entity-relationship-diagram/">What is Entity Relationship Diagram (ERD)?</a></p><h4>Step 2: Django Startproject …</h4><p>Create a new repository, clone it, and start a new django project in it.</p><pre>% sudo pip3 install pipenv<br>% pipenv shell -&gt; this automatically creates a virtual environment<br>% pipenv install django<br>% django-admin startproject Relay<br>% cd Relay<br>% django-admin startapp user -&gt; add any app<br>% python manage.py runserver</pre><p>If you are totally lost, I recommend you to try the official django tutorial.</p><p><a href="https://docs.djangoproject.com/en/4.1/intro/tutorial01/">Writing your first Django app, part 1 | Django documentation | Django</a></p><h4>Step 3: Connect your django project to your database</h4><p>As we used Postgres as our database, I downloaded the Postgres app and created a new database in my local server using the given terminal.</p><pre>postgres=# CREATE DATABASE relayapp;<br>relayapp=# \dt -&gt; shows tables</pre><p>Then, I changed the database information in the ‘settings.py’, and made migrations to connect to the database. When finished, the ‘relayapp’ had data tables in them!</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f80b2c591d85f615e627c4a957791d0b/href">https://medium.com/media/f80b2c591d85f615e627c4a957791d0b/href</a></iframe><pre>% pipenv install psycopg2<br>% python manage.py makemigrations<br>% python manage.py migrate<br>% python manage.py createsuperuser<br>% python manage.py runserver</pre><h4>Step 4: Create a Model of the entities</h4><p>A model is the single, definitive source of information about your data. It contains the essential fields and behaviors of the data you’re storing. Generally, each model maps to a single database table.</p><pre>% django-admin startapp story</pre><p>First start a new app, for me I started a ‘story’ app to put all information related to a novel.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8d271ac76476535686f3558bfa7e4e44/href">https://medium.com/media/8d271ac76476535686f3558bfa7e4e44/href</a></iframe><p>Then write down essential fields and behaviors of the data according to the ERD made in the first step.</p><h4><strong>Step 5: Install Djangorestframework, and create Serializer for easy use</strong></h4><pre>% pip install djangorestframework</pre><p>Serializer can easily convert complex data such as queryset and model instances into JSON, XML, or other content types. The serializer also validates the data received and then provides serialization to allow for type conversion to complex types. The serializer of the REST framework behaves similarly to the Django form and ModelForm class.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/045848bdd20207a883799a11c669721f/href">https://medium.com/media/045848bdd20207a883799a11c669721f/href</a></iframe><p>This is a serializer for the creation of the entity.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4de4e2ff3e83aa4e0c7ddcb193e6e639/href">https://medium.com/media/4de4e2ff3e83aa4e0c7ddcb193e6e639/href</a></iframe><p>This is a serializer to get other informations of the story.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9cccec58f608339c5532490ca21711a1/href">https://medium.com/media/9cccec58f608339c5532490ca21711a1/href</a></iframe><p>Don’t forget to link it with urlpatterns.</p><h4>Step 6: Create Views and add any functions you need</h4><p>A view is a place where we put the “logic” of our application.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/df04fbef8a60fc3b403121a09da3c1b1/href">https://medium.com/media/df04fbef8a60fc3b403121a09da3c1b1/href</a></iframe><p>A ViewSet class is simply a type of class-based View, that does not provide any method handlers such as .get() or .post(), and instead provides actions such as .list() and .create().</p><h4>Step 7: Make Migrations!</h4><pre>% python manage.py makemigrations<br>Migrations for &#39;user&#39;:<br>  user/migrations/0001_initial.py<br>    - Create model User<br>Migrations for &#39;story&#39;:<br>  story/migrations/0001_initial.py<br>    - Create model Story</pre><pre>% python manage.py migrate<br>Operations to perform:<br>  Apply all migrations: admin, auth, contenttypes, sessions, story, user<br>Running migrations:<br>  Applying user.0001_initial... OK<br>  Applying story.0001_initial... OK</pre><p>If you did everything right, your data will be migrated. Migrations is a process of applying changes to the DataBase schema.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*n14GT2BZ6-pH2hcfaEAldQ.png" /></figure><p>You can find out that tables are added in the Postgresql app.</p><h4>Step 8: Repeat steps 4 to 7 until you get all the views for the features of your app</h4><p>You should make a checklist of what the server needs to do. Do the chores one by one, by making a new app or adding a serializer. Here is a simple list I referred to while making our “Relay” app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bo9BtyNDeIouHJRywIACuA.png" /></figure><h4>Step 9: Connect your Database to AWS server before you forget it</h4><p>When you work on a project together with your teammates, it is really inconvenient to work on your localhost. So it’s really sooner the better. Even you are on your own, make sure to connect your database to the cloud server so that it becomes serviceable.</p><p><a href="https://aws.amazon.com/ko/rds/postgresql/">Amazon RDS for PostgreSQL - Amazon Web Services(AWS)</a></p><ul><li>Create an aws ec2 instance server</li><li>Create aws rds</li><li>Set up for remote access with ssh</li><li>Set up a development environment within an instance server</li><li>Connect rds to the instance server</li></ul><p>Afterwards, you can enter the server easily like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*28nTu8WL836AB0Ugft3Rlw.png" /></figure><h4>Step 10: Make test files to test your codes</h4><h4>Step 11: Create an API document for your service client</h4><p>In the case of our team, the process was unnecessary because the server team was in charge of creating API files, but it is essential for smooth communication with client developers in normal cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vHdX0GncREwWXkcLb3TTxg.png" /></figure><p>Testing with the API is also recommended, since there may be some issues regarding the client.</p><h4>Step 12: Buy a domain if you wish, and s<strong>witch from HTTP to HTTPS</strong></h4><p>Purchasing a domain provides convenience such as not having to enter a port number, and also provides convenience when setting up redirecturl. It may also be necessary to implement some social logins.</p><p>And most of all, purchasing a domain is essential if you want the url to be starting with HTTPS, following the security protocol.</p><p><strong>[Steps for switching to HTTPS]</strong></p><ol><li>Acquire &amp; Install an SSL Certificate.</li><li>Add HTTPS Version to Search Console.</li><li>Set up 301 redirects.</li><li>Change All Internal Links.</li><li>Fix Mixed Content Issues.</li><li>Make Sure Everything Works Properly.</li><li>Resubmit Disavow File &amp; Change Your Backlinks.</li></ol><p>Probably that’s it. Or there may be several unexpected issues. No matter how things are going, wish you good luck and welcome to Django! If you have any questions, please feel free to ask.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21c3b1a8109f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Show Location on a Map with MapKit]]></title>
            <link>https://medium.com/@chaemin2001/show-location-on-a-map-with-mapkit-b48ff663d066?source=rss-43e26c27c766------2</link>
            <guid isPermaLink="false">https://medium.com/p/b48ff663d066</guid>
            <category><![CDATA[uikit]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mapkit]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Chloe Lee]]></dc:creator>
            <pubDate>Tue, 23 Aug 2022 05:12:36 GMT</pubDate>
            <atom:updated>2022-09-21T06:59:23.139Z</atom:updated>
            <content:encoded><![CDATA[<p>For the past 6 weeks, our team worked on an app named ‘Yetda’(Korean word for “here you go”). ‘Yetda’ is for people who likes to travel abroad, and buys gifts or souvenirs for close friends or coworkers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_WgVfeexREbpcUA6IKshgA.png" /></figure><p>Although many people enjoy choosing and delivering gifts, they feel upset when they don’t get the wanted response. So we made this app to deliver the process and story of buying a gift. One of the key features is to show where the gift was bought, and show it with Apple Map in Collection View.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qQvhpQKgyMpChrcjMtPMcg.png" /></figure><p>So we decided to use Mapkit, and it is shown in the Detail View as above.</p><h4>Import Mapkit and set CLLocationManager</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8c79249af26ac0a3eb1e9cda82ddc8a7/href">https://medium.com/media/8c79249af26ac0a3eb1e9cda82ddc8a7/href</a></iframe><h4>Make Functions to Indicate a Location</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d00b0d0328eb43ae82fdc8b11550d30e/href">https://medium.com/media/d00b0d0328eb43ae82fdc8b11550d30e/href</a></iframe><h4>Recall function with Location Data</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/48032a46400045b04014ec3bfe19119b/href">https://medium.com/media/48032a46400045b04014ec3bfe19119b/href</a></iframe><p><strong>Here is the full code for our app, and you will be able to find the files you were looking for. Most of our codes are still in Develop Branch.</strong></p><p><a href="https://github.com/shinehardd/Yetda-iOS">GitHub - shinehardd/Yetda-iOS</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b48ff663d066" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Things to Consider when Planning App Ideas]]></title>
            <link>https://medium.com/@chaemin2001/3-things-to-consider-when-planning-app-ideas-6d29aa4a6ae7?source=rss-43e26c27c766------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d29aa4a6ae7</guid>
            <category><![CDATA[app-distribution]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[app-planning]]></category>
            <dc:creator><![CDATA[Chloe Lee]]></dc:creator>
            <pubDate>Mon, 22 Aug 2022 07:22:13 GMT</pubDate>
            <atom:updated>2022-08-22T07:22:13.910Z</atom:updated>
            <content:encoded><![CDATA[<h3>3 Things to Consider when Planning App Ideas: based on my experience of prototyping 3 apps with my teammates</h3><p>As a University student majoring in Computer Science, I had experience in implementing features on apps, but never experienced planning them myself. After joining Apple Developer Academy in South Korea, I had to perform as a Product Manager, UI/UX Designer, and iOS Developer at the same time to keep the team running.</p><p>So based on my experience of prototyping three apps with my teammates, I would like to introduce our work flow and give out several recommendations regarding planning app ideas.</p><h4><strong><em>We applied Challenged Based Learning, or CBL Framework Process</em></strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*MdDjmXQ44QKMO44ZLZd4bQ.png" /></figure><p><a href="https://www.challengebasedlearning.org/framework/">Framework - Challenge Based Learning - CBL Framework</a></p><p>According to the site above, Challenge Based Learning is introduced as a collaborative and hands-on foundation for learners. It is divided into three interconnected phases: Engage, Investigate and Act.</p><p>During the <strong>“Engage”</strong> phase, the team moves from an abstract big idea to a concrete and actionable challenge using the Essential Questioning process. First, we collect each of our interests and generate the <strong>Big Idea</strong> with it. A Big Idea is a broad concept that can be explored in multiple ways. Next we discuss personal and contextual questions about the big idea, and the most outstanding question becomes Our <strong>Essential Question</strong>. Then we brainstorm to expand the essential question and generate multiple challenge statements. The created <strong>Challenge</strong> will turn the Essential Question into an action statement.</p><p>The next phase would be <strong>“Investigate”</strong>. The investigation phase is divided into general investigation, domain investigation, and applied investigation. <strong>General Investigation</strong> is driven by guiding questions which helps teammates understand and clarify the full context of the Challenge. Starting from the challenge, we generate as many questions we can and all the things needed to explore and learn to accomplish it. After this process, the challenge may be refined or changed.</p><p>The next step is mapping the domain to the challenge through <strong>Domain Investigation</strong>. We organize the actors of our problem and list out what they need, want, or wish and the reason behind such behavior. These would be articulated into a single <strong>Problem or Opportunity Statement</strong>. This is when we finally brainstorm possible solutions. There may be several criteria the team agrees on, and we determine the most interesting and feasible <strong>Solution Concept</strong>.</p><p>Final <strong>Applied Investigation</strong> is moving from a solution concept to a validated prototype. To design User Experience, we have to define the models of potential users, or <strong>Persona</strong> in short. Demographic information, goals, needs, actions, priorities, pain points, obstacles, or any kind of description is allowed. This persona would help the team come up with <strong>User Stories</strong>, which describes the situation when a solution is needed during the experience of the persona. An <strong>App Statement</strong> is what puts all of this together in one sentence. This is the end of the App Planning Stage.</p><p><strong>Lo-Fi Prototyping, Branding, Hi-Fi Prototyping, App Development and Distribution</strong> would take place in the<strong> “Act”</strong> phase. This step is where we implement the solution with an authentic audience to see if it effectively solves the Challenge.</p><p>All this process requires constant retrospective and feedback from each teammate. Throughout this process, I was able to convince myself and teammates about the app idea and finalize our reasons and thoughts behind the app.<strong> Nevertheless, I would like to introduce some of the wrong ideas that a novice app developer can have.</strong></p><ol><li><strong>Make sure your App does not depend solely on social interaction or group of influencers</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ByyFA1G1BM8daUIhMfHXOg.jpeg" /></figure><p>A group of people has strong influence, and even a slight fact that a majority of people is using a particular service or app can be appealing to potential users. This is because social interaction itself has high economic value, and people are always interested in the lifestyle of influencers or celebrities. Many apps do rely on such human behaviors and make a huge profit out of it. When it is your first time brainstorming app ideas, it’s likely to rely on this fantasy.</p><p>Reality is not that easy. When you launch a new app, there will only be a few hundred or a few thousand users even it’s a fine and working app. To maintain the users, there must be a clear reason why he or she should consistently use the app even the user population is not large.</p><p>Our first app idea “Qlog” didn’t have an answer to such question. Asking a question to your personal role model or celebrity is only possible when he or she is our user in the first place. In other words, if we fail to invite them, no one will find our service attractive. <strong>We were confident about the experience we wanted to provide to our users, but did not have any clue of how to make it happen.</strong></p><p>Ever since I faced this problem and failed to distribute our app, I always check if the app service is worth using even if the user uses it alone. Relying on social interaction may be a smart idea, but it should not be the only appealing factor to potential users.</p><h4>2. Design your App Flow and User Experience based on Persona’s lifestyle pattern, not yours</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k4KkVLVrd6yZSgkZRw14nw.jpeg" /></figure><p>Our second app “Cleanny” was based on my personal experience of living alone. Since there was no one to check if I am living in a clean and neat environment, it was too easy to put off cleaning. Besides, house chores is not a self-satisfying activity compared to studying or exercising.</p><p>So the aim was clear, to motivate users to clean their room or house. At first, our lo-fi design included a checklist to check the cleaning schedule, and chores were divided into more detailed actions. For instance, laundry was divided into running the washing machine, drying, and putting clothes in the closet. <strong>But these were the function I wanted, not the service our persona wanted.</strong></p><p>Our personas were lazy people who put off cleaning frequently and browse through the internet or social media in the meantime. What they needed was a strong sign that they should clean up immediately. So we modified the main features into checking the overall state of your room with a character, and checking the status of your friends. This was more intuitive for first-time users, and we were able to focus on our challenge, “motivation”.</p><p>Through this experience, I got to understand the importance of Persona and Creating User Story stage, and was able to get user feedback that it was cute and fun to use the app.</p><h4>3. Confirm your App Technology Stacks before actual development</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kraKhFvyZUqZ-E8ubLQVnA.jpeg" /></figure><p>App ideas are important, but it is all useless if it is hard to implement into a working app. <strong>So it is most important to check what technology stacks are needed and whether your development teammates are familiar with them.</strong> Not only does this shorten the development period, it’s also very helpful when describing apps. Here are several tech stacks to refer to, provided by Apple Academy.</p><ul><li>3rd Party Framework Integration</li><li>App Clips</li><li>Apple Pencil</li><li>Audio / Video</li><li>Augmented Reality</li><li>Cloud Data</li><li>Computer Graphics (2D, 3D, Animation)</li><li>Computer Vision</li><li>Custom Camera</li><li>Custom Keyboard</li><li>Game Development (SptiteKit, Meta, Vision …)</li><li>Geo Location</li><li>Gesture Recognition</li><li>Haptic Feedback</li><li>Health Framework (Health Kit, Care Kit)</li><li>In-App Purchase</li><li>Internet of Things (IoT)</li><li>Machine Learning</li><li>Motion and Gyroscope</li><li>Multi-Lingual</li><li>Networking</li><li>Notification</li><li>On-Device Data Storage</li><li>Peer to Peer</li><li>Privacy and Security</li><li>SwiftUI</li><li>Voice Assistance</li><li>Widget</li></ul><p>I hope this article became a somewhat guide to planning app ideas!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d29aa4a6ae7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Difference between iOS Frameworks]]></title>
            <link>https://medium.com/@chaemin2001/difference-between-ios-frameworks-swiftui-uikit-928f147866b1?source=rss-43e26c27c766------2</link>
            <guid isPermaLink="false">https://medium.com/p/928f147866b1</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[uikit]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Chloe Lee]]></dc:creator>
            <pubDate>Thu, 14 Jul 2022 13:12:44 GMT</pubDate>
            <atom:updated>2022-07-21T06:31:32.345Z</atom:updated>
            <content:encoded><![CDATA[<h3>Difference between iOS Frameworks : SwiftUI? UIKit?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*F1jyIneFFOOfmNS_mdSZHQ.png" /><figcaption>SwiftUI? UIKit?</figcaption></figure><p>When it comes to choosing the right framework for your app, many programmers rely on the experience of fellow developers. There are still not much information about SwiftUI on Google, and it is estimated that at least 3 years are left until a complete paradigm shift to SwiftUI from UIKit. But in recent cases, SwiftUI is quite frequently used when refactoring old and outdated codes. In this post, I would like to compare key differences between two frameworks.</p><p>According to Apple Developer Documentation, the major difference between two frameworks is that <a href="https://developer.apple.com/documentation/swiftui/">SwiftUI is declarative</a>, when <a href="https://developer.apple.com/documentation/uikit/">UIKit is imperative</a>. Simply put, the declarative type lists what to do, and the imperative type implements how to do it.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e5fefdef9df8c747aaff84775241724f/href">https://medium.com/media/e5fefdef9df8c747aaff84775241724f/href</a></iframe><p>Here is a simple code to make a View named CardView in SwiftUI.</p><p>The @State var indicates that the data is automatically bonded to your var and your UI element also, and the framework will keep track of the state changes for you. All the codes are there to declare how the UI should look like, and how it should behave.</p><p>This comes with a major drawback, that it is hard to draw the view in detail from the code itself. This is why SwiftUI provides live preview, allowing developers to keep track of the UI they are drawing and check changes immediately. Apple provides strong preview assets, such as allowing easier darkmode optimizations.</p><figure><img alt="https://medium.com/swlh/integrating-swiftui-with-uikit-and-developing-xcode-previews-for-uikits-viewcontroller-39941aaf2392" src="https://cdn-images-1.medium.com/max/1024/0*OuiMK6sd4C7kidoE.png" /><figcaption>UIKit storyboard</figcaption></figure><p>In UIKit, it is possible to use drag-and-drop to build user interfaces and connect outlets onto the code. However, code base building is a more preferred way, since it prevents future conflicts when working as a team.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/474ef8c1ee74bd394ad4bc709789ec29/href">https://medium.com/media/474ef8c1ee74bd394ad4bc709789ec29/href</a></iframe><p>This is a simple piece of code to draw a ViewController, the code is written in an imperative way, guiding how to draw a view, from placing a scrollview on top of the view and adding a subview to it.</p><p>When building UI with code, UIKit tends to result in longer code lines compared to SwiftUI. So, many developers usually declare the looks of each UI element separately with a function like setScrollView() above, while leaving the viewDidLoad() action lightly as possible.</p><p>This is a simple introduction to SwiftUI and UIKit. Many current developers integrate two frameworks to boost work efficiency.</p><p>Still, apart from anything else, UIKit is much better in terms of documentation and support. Many of Apple’s frameworks were built on top of UIKit, and most of apps on App Store is built with UIKit. This means that implementing different frameworks on top of SwiftUI can result in unexpected errors, and it may be more safe to start any new project with Storyboard interface.</p><p>But SwiftUI is a lot easier and convenient. In some cases, it figures out what you intend the view to look like for you. For instance, many of the animations on SwiftUI is done simply with a code .withAnimation().</p><p>I highly recommend developers to experience both frameworks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=928f147866b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[iOS Example .com]]></title>
            <link>https://medium.com/@chaemin2001/ios-example-com-where-you-can-find-amazing-packages-and-customize-for-your-app-38018fbda4e2?source=rss-43e26c27c766------2</link>
            <guid isPermaLink="false">https://medium.com/p/38018fbda4e2</guid>
            <category><![CDATA[libraries]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[pencilkit]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Chloe Lee]]></dc:creator>
            <pubDate>Mon, 04 Jul 2022 04:00:20 GMT</pubDate>
            <atom:updated>2022-07-21T07:29:53.539Z</atom:updated>
            <content:encoded><![CDATA[<h3>iOS Example .com : where you can find amazing packages and customize for your app</h3><p>PencilKit of Apple is pretty good framework, and it enables you to incorporate drawing content into your app. However, there are still several problems such as that you cannot use it on top of PDFKit; Apple just says no.</p><p>So there are several alternatives, and one is to find out a swift drawing library on the internet. The link below is from “iosexample.com”, where you can find amazing packages with elaborate descriptions.</p><p><a href="https://iosexample.com/a-fast-and-complete-swift-drawing-library/">A Fast and Complete Swift Drawing Library</a></p><p>So this is the package I used; FastDraw of collinzri. FastDraw is a drawing library that supports Apple Pencil. It provides a pen, highlighter, eraser, lasso, and export files in either PDF, sqlite, or png.</p><p><a href="https://github.com/collinzrj/FastDraw?ref=iosexample.com">GitHub - collinzrj/FastDraw: A Fast and Complete Swift Drawing Library</a></p><p>Here is what I made by using the library. Full code is available in the link below. Due to several problems, I uploaded the whole file in zip file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0YHiielEm9RVnC-VptuKNA.gif" /></figure><p><a href="https://github.com/chaemin2001/FastDraw-Customize.git">GitHub - chaemin2001/FastDraw-Customize</a></p><ol><li><strong>Add a UIColorPickerViewController for color selection, and add buttons for user tool choice.</strong></li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1179b54d967deaffa2413ef43ad5b3ee/href">https://medium.com/media/1179b54d967deaffa2413ef43ad5b3ee/href</a></iframe><p><strong>2. Set the symbol image for each button, and set colors for selection</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/17a50c7785afea5020e29560a3077b0c/href">https://medium.com/media/17a50c7785afea5020e29560a3077b0c/href</a></iframe><p><strong>3. Insert the DrawBoardView provided from ‘FastDraw’ and set delegates if necessary.</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4588444557b9179f3ec0ac1304b726ce/href">https://medium.com/media/4588444557b9179f3ec0ac1304b726ce/href</a></iframe><p><strong>4. Make sure other buttons change state to unselected when another tool is touched.</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d714efd04d4ad6a40f966bbbd8fa0eb8/href">https://medium.com/media/d714efd04d4ad6a40f966bbbd8fa0eb8/href</a></iframe><p><strong>5. Make sure to include the operationEnded function in your code.</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7ffac110c7c84ebc1c1519f424917ff1/href">https://medium.com/media/7ffac110c7c84ebc1c1519f424917ff1/href</a></iframe><p>However, I did not include this library in <a href="https://medium.com/@chaemin2001/simple-introduction-to-pencilkit-draw-on-an-image-with-zoom-in-and-out-features-1f8c8f78e803">my drawing module</a> due to several limitations. First, I was not able to understand the DrawBoard as well as about PKCanvasView, and therefore zooming in or scrolling features was more hard to make. Next, although the tools were drawable, their performance was not as sensitive or sophisticated compared to PencilKit. To make full use of Apple Pencil’s features, PencilKit may be the best answer.</p><p>Still, I was amazed at how the line width changes depending on the force that goes onto the screen. There was much to learn, and I highly recommend developers to take a look in <a href="https://iosexample.com/">https://iosexample.com/</a>, and try customizing for your app.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38018fbda4e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple Introduction to Pencilkit]]></title>
            <link>https://medium.com/@chaemin2001/simple-introduction-to-pencilkit-draw-on-an-image-with-zoom-in-and-out-features-1f8c8f78e803?source=rss-43e26c27c766------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f8c8f78e803</guid>
            <category><![CDATA[uikit]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[pencilkit]]></category>
            <category><![CDATA[drawing-tablet]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Chloe Lee]]></dc:creator>
            <pubDate>Wed, 29 Jun 2022 20:03:33 GMT</pubDate>
            <atom:updated>2022-07-21T06:33:11.620Z</atom:updated>
            <content:encoded><![CDATA[<h3>Simple Introduction to Pencilkit: draw on an image! with zoom in and out features</h3><p>Hello, this is Chloe again. I would like to introduce ‘Pencilkit’ on UIKit. Pencilkit works perfectly with UIKit because its PKCanvasView is designed to be placed on top of UIScrollView.</p><p>I wished to make a zoomable, scrollable, and drawable module with an image in the background so that the image zooms and scrolls with the handwriting concurrently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cx3tcqkF74iSwwLKbzjMzg.png" /><figcaption>Captured Image of Simulator</figcaption></figure><p><strong>You can find the full code of this module in the link below ⬇️</strong></p><p><a href="https://github.com/chaemin2001/Dongurami-PencilModule.git">GitHub - chaemin2001/Dongurami-PencilModule: 동그라미 펜슬 모듈</a></p><h4><strong>1. Set a Scrollable and Zoomable Module View</strong></h4><ul><li>Set the initalizer with leadingScale, widthScale, and heightScale each indicating the ratio relative to the whole screen.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b9277b8a1512b21d687de74443391112/href">https://medium.com/media/b9277b8a1512b21d687de74443391112/href</a></iframe><ul><li>Keep the module within the bounds of the screen.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/996712603e84859976236e743ffc96ca/href">https://medium.com/media/996712603e84859976236e743ffc96ca/href</a></iframe><ul><li>To make the screen look identical in portrait and landscape mode, check the orientation of the UIDevice and change the layout each time screen rotation is invoked. Specify a new array variable that contains NSLayoutConstraint to find out the exact constant to the anchor. This would enable the module to maintain the same size ratio in the landscape mode, but sometimes shorter, depending on the size of the image.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bef6ca4eee1b20c497725dd6ac3b29af/href">https://medium.com/media/bef6ca4eee1b20c497725dd6ac3b29af/href</a></iframe><h4>2. Add PKCanvasView as a Subview of the ModuleView</h4><ul><li>Allow the canvas view to scroll within the frame of the picture</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/587e522589f7ff73e680a63dc7f946d6/href">https://medium.com/media/587e522589f7ff73e680a63dc7f946d6/href</a></iframe><ul><li>Let the frame of the canvas view be the frame of the module</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9cf8e260d9581e9637128973cacaee9a/href">https://medium.com/media/9cf8e260d9581e9637128973cacaee9a/href</a></iframe><ul><li>Set the zoomlevel to be the (screen’s height / screen’s width) in both orientations.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/50eee7817653d31b11327c7a199fa677/href">https://medium.com/media/50eee7817653d31b11327c7a199fa677/href</a></iframe><h4>3. Set a Background Picture for Drawable CanvasView</h4><ul><li>Insert the image as the subview of the canvasView.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2949527519c5e928b418eb862f3e642b/href">https://medium.com/media/2949527519c5e928b418eb862f3e642b/href</a></iframe><ul><li>Let the picture’s width be the width of the module. Set it again when the screen is rotated.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/46812b680017974b35165ebcb222958a/href">https://medium.com/media/46812b680017974b35165ebcb222958a/href</a></iframe><ul><li>If the module’s length is longer than the length of the item picture, resize the module’s frame, and if it’s shorter, make the picture scrollable within the module.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/83f033929e949a44a20ec135d3c808a1/href">https://medium.com/media/83f033929e949a44a20ec135d3c808a1/href</a></iframe><h4>4. Add PKToolPicker to the View, which Hovers Over the Screen</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ae6e36d308aaba352f195c150ddd0573/href">https://medium.com/media/ae6e36d308aaba352f195c150ddd0573/href</a></iframe><h4>5. Save and Load the Drawing using the UserDefaults Data</h4><ul><li>Create a storage class using UserDefaults. Sort, store, and recall with id for each case.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/816d35e0c36cdf832dfa9d39274d7703/href">https://medium.com/media/816d35e0c36cdf832dfa9d39274d7703/href</a></iframe><ul><li>Save the drawing data each time the button is tapped.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ff9bd6b2e27b3e7a2caeb0912fba2453/href">https://medium.com/media/ff9bd6b2e27b3e7a2caeb0912fba2453/href</a></iframe><ul><li>Load the drawing data when toolkit is loaded.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3af940cebf68a1c2ff5c5790b953033f/href">https://medium.com/media/3af940cebf68a1c2ff5c5790b953033f/href</a></iframe><h4>6. Additional Feature) Multi ModuleView</h4><ul><li>Create a module class that inherits the UISrollView within the View Controller. Manage the modules with an array in ModuleScrollView. Most functions are defined in ModuleScrollView except for saving, screen rotation, and screen display.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6624dead85616ea7a8cc319cd0198cc1/href">https://medium.com/media/6624dead85616ea7a8cc319cd0198cc1/href</a></iframe><ul><li>Later created modules can be overlapped on top of the former module. Scroll, zoom, save, and drawing all works fine.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9ca4f5d51f90f98965c59c058310635e/href">https://medium.com/media/9ca4f5d51f90f98965c59c058310635e/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f8c8f78e803" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sharing Core Data with Cloudkit in SwiftUI]]></title>
            <link>https://medium.com/@chaemin2001/sharing-core-data-with-cloudkit-in-swiftui-94536ad61133?source=rss-43e26c27c766------2</link>
            <guid isPermaLink="false">https://medium.com/p/94536ad61133</guid>
            <category><![CDATA[cloudkit]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[cloudkit-sharing]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[new-app-technology]]></category>
            <dc:creator><![CDATA[Chloe Lee]]></dc:creator>
            <pubDate>Thu, 23 Jun 2022 07:38:05 GMT</pubDate>
            <atom:updated>2022-07-21T07:35:06.355Z</atom:updated>
            <content:encoded><![CDATA[<p>For the past 6 weeks, our team worked on an app named ‘Cleanny’, which is now also available on App Store.</p><p><a href="https://apps.apple.com/kr/app/cleanny/id1630640491">https://apps.apple.com/kr/app/cleanny/id1630640491</a></p><p>‘Cleanny’ is for people who are not motivated to clean up their house and do the daily household routines due to lack of energy. Our app provides four types of character, each representing the state of chores done.</p><p>We manage the user’s data with CoreData, and used Cloudkit to implement one of the core features of the app, ‘sharing your character with friends’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/1*9q8DF0ESgIYP14Ib4y2cBQ.png" /></figure><p>This is a simulation of our core feature “sharing”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/1*K9iBNlqqCkRnEkgzfz4mSw.gif" /><figcaption>Cleanny App on iPhone13</figcaption></figure><p>Since it was my first time dealing with Cloudkit, I refered to sample codes provided in the link below.</p><p><a href="https://www.raywenderlich.com/29934862-sharing-core-data-with-cloudkit-in-swiftui">Sharing Core Data With CloudKit in SwiftUI</a></p><p><strong>simple warning:</strong> The code in the link works well until before the sharing stage. If you need any tip to make the sharing happen, take a look at the instructions below.</p><p>The original plan was to connect the ‘User’ Model of core data directly to cloudkit so that the data on the cloud would update automatically each time the core data is changed. In order to do this, you have to set the configuration of the core data as below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZaijBTpY4AZGZAFM_6Hvhg.png" /><figcaption><a href="https://developer.apple.com/documentation/coredata/mirroring_a_core_data_store_with_cloudkit/setting_up_core_data_with_cloudkit">https://developer.apple.com/documentation/coredata/mirroring_a_core_data_store_with_cloudkit/setting_up_core_data_with_cloudkit</a></figcaption></figure><p>You will find further details ⬇️</p><p><a href="https://developer.apple.com/documentation/coredata/mirroring_a_core_data_store_with_cloudkit/setting_up_core_data_with_cloudkit">Apple Developer Documentation</a></p><h3>CloudkitUser.swift</h3><p>However, due to several problems regarding fetching CKRecord and CKContainer without an attribute whose type is ‘CKRecord’, I decided to make another model named ‘CloudkitUser’, and fetch and save data through the model.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4b3e18c51869db7ee2c5cbf58e686bbb/href">https://medium.com/media/4b3e18c51869db7ee2c5cbf58e686bbb/href</a></iframe><h3>CloudkitUserViewModel.swift</h3><p>Then, a View Model with all the functions and enums to communicate with your cloudkit database will be needed. This view model should</p><ul><li><strong>check the state of the fetching process: whether it is loading, done with loading, or returned with an error</strong></li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/922cd113b9ad27adf0632ee683b803cc/href">https://medium.com/media/922cd113b9ad27adf0632ee683b803cc/href</a></iframe><ul><li><strong>initialize every time the View is refreshed, and create a cloudkit zone if needed</strong></li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5aa19b3c1a26392f00c0e699dcfc3bc2/href">https://medium.com/media/5aa19b3c1a26392f00c0e699dcfc3bc2/href</a></iframe><ul><li><strong>fetch data from both ‘Private Database’ and ‘Shared Database’ and return with type [CloudkitUser]</strong></li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/842e9447dd878a1c6dc69dc6c162ec4b/href">https://medium.com/media/842e9447dd878a1c6dc69dc6c162ec4b/href</a></iframe><ul><li><strong>update the data to the cloud when needed</strong></li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/63068217eabe890b141b010a85d7a7f7/href">https://medium.com/media/63068217eabe890b141b010a85d7a7f7/href</a></iframe><h3>CloudkitShareView.swift</h3><p>The next thing needed is the actual sharing view, where users can check who they are sharing with, and send links via iMessage.</p><p>Apple provides UICloudSharingControllerDelegate, so that it is easy to create such linking view. Here is the code for the view.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/26daea395535f757154cf36bf9943168/href">https://medium.com/media/26daea395535f757154cf36bf9943168/href</a></iframe><h3>ShareView.swift (or any View that you wish)</h3><p>The last but not least, is to load the data onto your view and link the cloudkit sharing view with some button or function.</p><p>First, get the ViewModel as an EnvironmentObject and name it as viewModel.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/00b82efb76177e23a5bd849e2c3de991/href">https://medium.com/media/00b82efb76177e23a5bd849e2c3de991/href</a></iframe><p>Next, make an asynchronous function to load data from cloudkit.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2cabd2a8f4b604bb3133a55c32407204/href">https://medium.com/media/2cabd2a8f4b604bb3133a55c32407204/href</a></iframe><p>Lastly, make a function to connect your view to the cloudkit sharing view.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d0e50efc44fe75e1f892a10cf02aaac5/href">https://medium.com/media/d0e50efc44fe75e1f892a10cf02aaac5/href</a></iframe><p><strong>Here is the full code for our app, and you will be able to find the files you were looking for.</strong></p><p><a href="https://github.com/shinehardd/Cleanny-iOS.git">GitHub - shinehardd/Cleanny-iOS: 오늘 청소 하셨나요?</a></p><h4>🚨<strong>Final: If your Cloudkit does not work after App Store distribution</strong></h4><p>Check if your Cloudkit Database is deployed for production. In many cases, it may be available only for development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UHyRq54Gn1cBViTGFpHnyQ.png" /></figure><p>If the message just below your cloudkit name informs that it has not been deployed for production, click the squared button on the left bottom and make changes.</p><p>Still, changes might not be made due to schema problems, then add the following to your AppDelegate.swift and try again.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5402712f1da49c0185e1f40778f45794/href">https://medium.com/media/5402712f1da49c0185e1f40778f45794/href</a></iframe><p><strong>Currently, there is a lack of cloudkit content on the Internet. The sharing feature was introduced only a year ago, and there are still minor bugs in the cloudkit itself. But hope you give it a try, keeping my story in mind!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94536ad61133" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Minimal Visual Design and Branding Tips for iOS Developers]]></title>
            <link>https://medium.com/@chaemin2001/minimal-visual-design-and-branding-tips-for-ios-developers-8baf69733785?source=rss-43e26c27c766------2</link>
            <guid isPermaLink="false">https://medium.com/p/8baf69733785</guid>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Chloe Lee]]></dc:creator>
            <pubDate>Thu, 12 May 2022 05:15:54 GMT</pubDate>
            <atom:updated>2022-05-18T06:53:50.428Z</atom:updated>
            <content:encoded><![CDATA[<h4>After Reading Apple’s Human Interface Guidelines</h4><p>Best design for apps is unobtrusive branding. However in many cases, developers forget this fact and make their users feel disconnected or distracted. But if you can check on a few points, your app’s user experience can improve a lot. From HIG document from Apple, I organized the contents into five pieces of advice.</p><ol><li><strong>Make Sure Your App Runs on Every Screen Size for a Certain Device</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o9rg-uD4_IW9W0t9L2EpGg.png" /><figcaption>iPad and iPhone</figcaption></figure><p>The UI elements should stay inside the borders of the screen, and should not obscure navigation bar, tab bar, toolbar, or other views. Apple provides safe area layout guide with standard margins for developers. This guide ensures appropriate insetting based on device and context. For instance, when keyboard is visible, the layout guide reduces the bounds of safe area.</p><p>Another concept you might as well remember is ‘Size Classes’. ‘Regular’ denotes expansive space and ‘Compact’ denotes constrained space. Because the size classes vary by device and the orientation mode, layout may not change as the way you want. Always consider the concept when designing a screen-rotating app.</p><p><strong>2. Retain from Using Animation and Motion Effects Excessively</strong></p><p>Worst animation is animation for the sake of using animation. If your animation does not increase understanding or enjoyment of users, it would only make the app feel disorienting and difficult to control. Besides, make sure your animation does not defy physical laws. The key advantage of using animation should be to let people feel comfortable and natural, not to draw attention.</p><p><strong>3. Subtly Incorporate Your Brand Inside the App’s Design</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/1*UkTOCi0Qb2insJhwnLkmOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*5JKFz6r4-PdF_p7XkDxn5g.png" /><figcaption>Branding of Notes</figcaption></figure><p>“Subtly” neither refers to showing a persistent bar with brand assets nor displaying a logo throughout your app. This may be very tempting, but the users are not interested in your company, but only about the content they can get from your app. Successful brand design includes using custom color scheme or font, and designing the interface similar to the app icon.</p><p>For custom color scheme, it is best to pick a color palette that coordinates with your logo and stick to it. It is also recommended to provide two versions of the accent color, so that it looks natural in both light and dark modes.</p><p><strong>4. Create a Natural Launch Screen for New Users</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*SyihuIryaPqKI_b6lfjXRA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*1BsDb6h9N3y_NdUqV4avlQ.png" /><figcaption>launch screen and first screen</figcaption></figure><p>New users of your app would be unfamiliar with your screen layout. So it is important to design a launch screen that makes the transition to the first screen seem natural. Your launch screen should be kept minimal, without any kind of text because there may be localizing problems. Just in case, I inform you that your launch screen is not a splash screen. It is not a branding opportunity for your app. Logos are not recommended and natural transition should be prioritized when designing.</p><p><strong>5. Make Full Use of Materials</strong></p><p>iOS provides materials like blur effects to let views hint at background content without distracting from the foreground content. SF Symbols have great compatibility in this sense. Find out iOS defined materials such as SystemUltraThinMaterial, SystemThinMaterial, SystemMaterial, and SystemThickMaterial. Consider contrast and visual separation to choose the right material for your app.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8baf69733785" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Insights to make good use of Apple’s User Interface]]></title>
            <link>https://medium.com/@chaemin2001/10-insights-to-make-good-use-of-apples-user-interface-c897b00e7c9a?source=rss-43e26c27c766------2</link>
            <guid isPermaLink="false">https://medium.com/p/c897b00e7c9a</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Chloe Lee]]></dc:creator>
            <pubDate>Sat, 07 May 2022 11:59:34 GMT</pubDate>
            <atom:updated>2022-05-07T11:59:34.544Z</atom:updated>
            <content:encoded><![CDATA[<h4>After Reading Apple’s Human Interface Guidelines</h4><p>Apple offers a variety of delicate UIs. If you’re an iOS developer, you should be able to use those to provide a better experience for users who are already familiar with iOS features and animation. I would like to refer to the HIG document and introduce 10 UI tips that are essential to check on. I hope you would get a hint on how to design your App better.</p><ol><li><strong>Provide Comfortable Sign-in Experience</strong></li></ol><ul><li>Explain the reason the app is asking the user to create an account.</li><li>Keep most of the services available without an account.</li><li>Use “Sign in with Apple”, or with other social media and if else, use Password Autofill.</li><li>Account deletion is equally important.</li></ul><p><strong>2. Take Advantage of Apple Pencil Actively</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JHbKc7Hkb5o_fUJ9uuyFFg.png" /><figcaption>Apple Pencil 2</figcaption></figure><ul><li>Enable the Apple Pencil behaviors that people expect.</li><li>Allow smooth switch between ‘Apple Pencil’ and ‘Finger Input’.</li><li>For any kind of text controls (except password fields), allow ‘Scribble’.</li><li>Use ‘Pencilkit’ to let people draw on top of any content, such as PDF or photo.</li><li>Fixing the tool picker on one side is recommended when it might obscure other content.</li></ul><p><strong>3. Make Filling Out Information Easier</strong></p><ul><li>Present choices and default values.</li><li>Check the validity of field values dynamically.</li><li>Enable ‘Drag and Drop’ for photo or textline.</li></ul><p><strong>4. File Handling should feel Automatic</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*jtrtYENlAHsiwKtEZcQsPw.png" /><figcaption>App Files</figcaption></figure><ul><li>Files should be updated and saved at regular intervals or each time a new change is made.</li><li>Don’t make local-only files. Users expect their data to be available on other devices as well.</li><li>Use ‘File Provider Extension’ to share files with other Apps if possible.</li></ul><p><strong>5. Use ‘Standard Gestures’ only to perform ‘Standard Actions’</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*fGXffEtlJKkgGL5BI9-oMw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*1zwr3AKVsIhO9sLZ9Jc5uQ.png" /><figcaption>Typical Standard Gestures</figcaption></figure><ul><li>‘Standard Gestures’ include tap, drag, flick, swipe, double tap, pinch, three-finger pinch, three-finger swipe, touch and hold, rotate, and shake.</li><li>Each ‘Standard Gestures’ has expected actions, such as double tap and pinch for zoom and three-finger swipe and shake for redo or undo.</li><li>It’s best to utilize some of these features to enhance experience of Apps while not interfering with systemwide gestures.</li></ul><p><strong>6. Animation and Haptics are a Good Provider of Feedback to Users</strong></p><ul><li>Use standard UI elements such as switches, sliders, and pickers.</li><li>Predefined Haptic Patterns are provided with UIFeedbackGenerator in the categories of notification, impact, and selection.</li><li>Creating ‘Custom Haptic Patterns’ might enhance users’ experience especially when communicating in game.</li><li>‘Custom Haptic Pattern’ is made by combining transient and continuous events, varying sharpness and intensity, and including optional audio contents if needed.</li></ul><p><strong>7. Design your Keyboard Wisely, not to cause Trouble</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*HgRXnH5IjntSguOBAfL0Cw.png" /><figcaption>UI Fully Visible (O)</figcaption></figure><ul><li>Match the type of keyboard to the content people are filling in.</li><li>Ensure that other UI remains accessible while the keyboard is onscreen by using layout guide.</li><li>Support ‘Keyboard Shortcuts’ and ‘Keyboard Navigation’ on iPad.</li></ul><p><strong>8. Users are Familiar with Near Field Communication (NFC), so Get Used to It</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*Fy6etFd7EpRBlUy4cAc0ow.png" /><figcaption>Typical NFC</figcaption></figure><ul><li>Use terminology carefully, not to include expressions that indicate contacting with physical objects. For instance, ‘scan and hold’ is better than ‘tap and touch’.</li><li>Users are familiar with scanning action, but not with technical term ‘NFC’. Avoid using the word directly.</li><li>Provide short instructional text before scanning.</li></ul><p><strong>9. Enable Pointer Interactions for iPadOS</strong></p><ul><li>Use ‘Content Effect’ such as highlight, lift, and hover to change the UI element or region beneath the pointer.</li><li>‘Pointer Magnetism’ could help users target the element and draw out the expected actions.</li><li>Make sure there is enough padding around interactive elements to create comfortable hit regions.</li></ul><p><strong>10. Help People have Successful Nearby, or Spacial Interactions</strong></p><ul><li>‘Spacial Interaction’ tasks might resemble physical interaction in our everyday lives.</li><li>Prioritize nearby, contextually relevant information to enhance user’s experience.</li><li>Provide continuous and multiple types of feedback for the feel of engagement and holistic experience.</li><li>Encourage people to hold the device in portrait orientation.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c897b00e7c9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>