<?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 Kenzo Nawa on Medium]]></title>
        <description><![CDATA[Stories by Kenzo Nawa on Medium]]></description>
        <link>https://medium.com/@kenzonawa?source=rss-15bffb7ff2b6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*j62PqXHcs6hAhJfKo7Yh1w.jpeg</url>
            <title>Stories by Kenzo Nawa on Medium</title>
            <link>https://medium.com/@kenzonawa?source=rss-15bffb7ff2b6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:41:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kenzonawa/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 make a screen-by-screen prototype in Swift]]></title>
            <link>https://blog.prototypr.io/how-to-make-a-screen-by-screen-prototype-in-swift-7bbbe6543924?source=rss-15bffb7ff2b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bbbe6543924</guid>
            <category><![CDATA[prototyping-tools]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Kenzo Nawa]]></dc:creator>
            <pubDate>Mon, 19 Mar 2018 08:05:45 GMT</pubDate>
            <atom:updated>2018-03-19T08:05:45.934Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ever wish you could export your screens from Sketch into XCode?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V-OO7aBIGl-tFLvoE803Cg.jpeg" /></figure><p>Creating a prototype in Swift is not as hard as you think. A lot of people get intimidated by XCode’s interface because of its huge amount of buttons and options, but I’ve got good news for you: <strong>You can create a prototype without writing any code.</strong></p><p>I’ll be giving you a step-by-step guide on how you can create a basic prototype using Swift’s Storyboard. You’ll see that storyboards actually look similar to the design tools we use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RBu1JYeoEbKg_74gqsJggw.png" /></figure><h3>What you’ll need</h3><p>This prototype will be just like the ones made in inVision. We’re gonna add in our screens and place hotspots that link to other screens. All you’re gonna need is <a href="https://developer.apple.com/xcode/">XCode</a> and your screens as image files. If you don’t have screens to work on, you can <a href="http://kenzonawa.com/outsource/sketch-screens.zip">download</a> the ones I’ll be using.</p><blockquote><strong><em>Tip</em></strong><em>: Have your screens named </em>name<em>@1x, </em>name<em>@2x, </em>name<em>@3x so that XCode can automatically process them.</em></blockquote><h3>1. Creating a project</h3><p>When you open XCode, you should see a screen like this (without all the projects on the side). Let’s click on <strong>Create a new XCode project.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d1OT-_69OZ6ed4KeVIEdzg.png" /></figure><p>You’ll see a bunch of options here, but don’t worry about them. <strong>Single View App</strong> is the most widely used and can accommodate almost any app. Note that single view doesn’t mean it only handles one screen (which is what I thought at first).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8HnRvUEUJHiuviLubneTRw.png" /></figure><p>You can name your project anything. For this example, I’ll be naming it Prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CE-cZRlJ5FxCSWBOhx78tw.png" /></figure><h3>Don’t be overwhelmed</h3><p>When you create the project, this is the first screen you’re gonna see</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pTVf2bTVKQfi5-k3y2yRdw.png" /><figcaption>wow, that’s a lot to take in</figcaption></figure><p>Here’s what I want you to see</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lZ9nw44icvDk-Ol0GLitLQ.png" /><figcaption>That’s a little easier, right?</figcaption></figure><ol><li>These are the only two files we’ll be working with.</li><li>You’re probably familiar with this layout. The left panel shows document hierarchy and the right shows more information.</li><li>This is where you choose on which device you want to run your app.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*4AJ7K6lmOIKcZTa3C02mlg.png" /></figure><p>Let’s switch to iPhone 8 because that’s the default screen size on the Storyboard.</p><h3>2. Importing your screens from Sketch</h3><p>Click on <strong>Assets.xcassets</strong> and drag your images files</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*24f7apY1BtSANc61gAFS7w.png" /></figure><p>Once they’re imported, you should see that XCode automatically groups them by resolution type.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*EE6D8r3rmv3m7O48BZ_42g.png" /></figure><p>Now let’s move on to the Storyboard!</p><h3>Storyboards</h3><p>Here’s what it looks like</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ROFyAO8HHoKOgpnxaPBjmw.png" /></figure><p>You can hide the left panel because we won’t be navigating our project anymore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5J4ge-GnMCz88agl5FjlZQ.png" /></figure><ol><li>Close the left panel</li><li>The Object Library — This is where we add elements to our View Controller.</li></ol><h4>What’s a View Controller?</h4><p>In storyboards, you can think of view controllers as artboards in Sketch. If you have 5 different screens, you’re gonna have 5 different view controllers.</p><p>If you get into coding, however, view controllers are much more than that. They are the ones that handle all the logic for a given screen.</p><h3>3. Adding a screen</h3><p>Search for “Image” in the Object library. You should see <strong>Image View</strong> as the only result. Let’s drag it from the library to inside the view controller. You should see your image somewhere inside the view controller.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eDK2g5tucS9_WcpjAr1s_w.png" /></figure><ol><li>Constraints — This is where you add your Auto Layout constraints, so that your app is responsive.</li></ol><p>Let’s can click on the <strong>Add New Constraints</strong> and add <strong>0’s</strong> to the top, bottom, leading(<em>left</em>) and trailing(<em>right</em>) constraints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*HtZB1KY0VtkVhabAozlq_g.png" /></figure><h4>Auto Layout</h4><p>Auto Layout works by specifying how far your chosen element should be from another element. XCode automatically detects the other element given the visual layout. So in this example, we are saying this image should be 0 pts apart from the edges of the screen.</p><h3>4. Selecting the image</h3><p>On the right panel, make sure you’re in the Attributes Inspector(it should be the default) and choose your screen from the <strong>Image</strong> <strong>dropdown</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/514/1*N8wj4uvhvukvLz7l5U6WAQ.png" /></figure><p>You should now see your first screen!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*msCanNdK8g9zGbVuRa5IrA.png" /></figure><h3>5. Creating hotspots</h3><p>We’re gonna be creating hotspots with invisible buttons. Back in the Object Library, search for “button”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*50JfOxyBeiBuKbRJa4EcxQ.png" /></figure><p>Drag it into wherever you want your hotspot to be and then resize it as you wish. Also, double click on it and delete the text, we don’t need that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LrChu3z2jARiJYPeIfkXWA.png" /></figure><h3>6. Creating another screen</h3><p>To add another screen, we just need to drag and drop a View Controller from the Object library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EZO8wAjaCghb3nudjszU5Q.png" /></figure><p>From here, let’s repeat steps <strong>3- Adding a screen</strong> and <strong>4- Selecting the image</strong> for our second screen.</p><h3>7. Making the transition</h3><p>To make a transition from the hotspot to another screen, click and drag with your right mouse button from the invisible button to the destination screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i602hI1ikaoQKthawfrfVg.png" /></figure><p>When you let go, choose <strong>Present Modally</strong> as your option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p2w9xUMRDn0yuxOYfUNDLw.png" /></figure><ol><li><strong>Segue</strong> — Segues are the name Swift has for screen transitions. You should now see a connection between your two screens and be able to see its attributes.</li><li><strong>Transition</strong> — Storyboards don’t have the fanciest built-in transition animations. The one I recommend is <strong>Cross Dissolve.</strong></li></ol><h3>8. Rinse and Repeat</h3><p>Now you know how to create screens and make connections between them! Just repeat the steps until you have your entire flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/1*UgI2GVlONb7Gl3y3Ybfi2A.gif" /></figure><p>At this point, feel free to run your project on the simulator. It should be working!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7GleobdsMELVljfQkGfn3A.gif" /></figure><h3>That’s it!</h3><p>This was a basic prototype, but I hope you’re a bit more familiar with XCode and Swift now. I’d never thought of Swift as a prototyping tool, but I accidentally got the hang of it when I was building an app for myself, and realized that it’s much easier than I expected.</p><p>I think prototyping in Swift has a lot of unspoken benefits. Next time, I’ll show you a prototype that was only made possible with Swift (<em>hint: it uses maps</em>).</p><p><em>If you liked this guide and would like to learn other stuff with Swift, let me know in the comments!</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bbbe6543924" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/how-to-make-a-screen-by-screen-prototype-in-swift-7bbbe6543924">How to make a screen-by-screen prototype in Swift</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first app didn’t make it to the App Store]]></title>
            <link>https://medium.com/@kenzonawa/my-first-app-didnt-make-it-to-the-app-store-600820cf66a5?source=rss-15bffb7ff2b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/600820cf66a5</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[app-store]]></category>
            <dc:creator><![CDATA[Kenzo Nawa]]></dc:creator>
            <pubDate>Fri, 10 Nov 2017 18:27:57 GMT</pubDate>
            <atom:updated>2017-11-10T18:27:57.334Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*65pbU0Fp9KZFA7XFMeM_ng.png" /></figure><p>I’ve always wanted to have an app on the AppStore. Kind of like how kids want to be superheroes when they’re growing up. It didn’t have to make money or become a business. I just wanted to see if I could somewhat “impact” the world. This is a story on how I designed, developed, and ultimately <em>failed</em> to put my app out in the world.</p><h3>The idea</h3><p>I wanted to start simple. I also wanted to make something that would be useful to me. I’ve had the idea of a quick and easy reminder app for a while.</p><p>It started back a few years ago when I still lived in São Paulo, Brazil. I was alone at home playing a video game with my dog sitting next to me. The telephone rang and it was my grandma, who wanted to talk to my mom about something (I can’t remember what). I said I would relay the message to her as soon as she got home. I got back to playing my video game and as you would have guessed it, I never remembered to tell my mom. The next day, we were going to my grandma’s for lunch and the one thing I remember was the disappointed look she gave me as she said: “You never told your mom, did you?” I was deeply saddened as I saw how I’d let her down. At that moment, I thought just how it all could’ve been fine if I had simply taken note. Hence the idea for my app. One that helps you <strong>set reminders as easily as possible</strong>.</p><h3><strong>Fuse Tools: My first build</strong></h3><p>Over my summer internship <a href="https://life.ai/">life.ai</a> , I became acquainted with <a href="https://www.fusetools.com/">Fuse Tools</a>, a tool like Ionic/React Native to develop apps for both iOS and Android in one go. Our lead developer was super excited about it and had just migrated some work from <a href="https://www.nativescript.org/">NativeScript</a> to FuseTools just to show how fast and easy it was. I decided to learn it as well and use it for my little project.</p><p>I spent the next few weeks designing and learning Fuse in my spare time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0oyXP3GXuL5OkeltRdLf_w.png" /><figcaption>Earlier designs</figcaption></figure><p>Fuse really showed itself easy to develop on. Once I had the hang of it, I could completely overhaul the UI within a few hours in code. The downfall of Fuse materialized when trying to build the functionality. I needed the reminders to be sent as notifications. I got the notifications to work, but they weren’t perfect.</p><p><strong>Fail Case:</strong> I could set up a reminder and then delete it. I would still get the notification for the deleted item.</p><p>Talk about janky.</p><p>I tried to find ways to overcome this, but the only solution was to go into Objective C code. Fuse had let me down in this regard.</p><h4><em>Note on Android</em></h4><p>I initially started with Fuse because I wanted to publish both for iOS and Android. However, I don’t have an Android phone and developing just for iOS proved itself to be enough of a challenge. I decided to continue only with iOS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*yFLT7pjdAu8J01OMnMbXZQ.gif" /><figcaption>Final design on Fuse. The time picker was not customizable.</figcaption></figure><h3>iTunesConnect</h3><p>My app wasn’t exactly the way I wanted it to be, but I knew that was as far as I was gonna get with Fuse, so I decided to take a shot at the App Store. I jumped on <a href="https://developer.apple.com/">Apple Developer</a> and <a href="https://itunesconnect.apple.com/">iTunesConnect</a> to get all the mumbo jumbo (<em>read: certificates, provisioning profiles, and IDs</em>) in order to submit to the App Store. A few guides and tutorials later, I had everything set up to submit for review.</p><p>I found out Apple takes quite a few days to review your app. I was anxious for the first few, but decided kick-start my next project. After all, I was almost finished with this one, right?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FQaoh3qmKzOFVK%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fhahaha-evil-laugh-creepy-smile-Qaoh3qmKzOFVK&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FQaoh3qmKzOFVK%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="342" frameborder="0" scrolling="no"><a href="https://medium.com/media/7e970226cad55f241f06ce76716394d3/href">https://medium.com/media/7e970226cad55f241f06ce76716394d3/href</a></iframe><blockquote><strong>Binary Rejected</strong></blockquote><blockquote><strong>Guideline 4.2 — Design — Minimum Functionality</strong></blockquote><blockquote>We found that the usefulness of your app is limited by the minimal amount of content or features it includes.</blockquote><p>What on earth was <a href="https://developer.apple.com/app-store/review/guidelines/#design">Guideline 4.2-Design-Minimum Functionality</a>? The more I read about it, the more concerned I got that it referred to not having enough features. The reason I wanted to build my app was so it could be easy to use. This meant not having a barrage of features on the user’s screen.</p><p>I was at an impasse.</p><p>On the bottom of their message I saw a tiny blue text that read: “Submit an appeal to the App Review Board”. I wrote them a huge letter explaining why the reason I made this app was, ironically, the same reason it got rejected. I even had a <a href="https://kenzonawa.github.io/24do/">landing page</a> ready!</p><p>After a few more days, I received what seemed like an automated message saying they determined their decision was still valid. At this point, I had 2 options: either keep trying to convince them or go back to the app. I opted for the latter. I also knew by now the constraints that Fuse had and that if I wanted to perfect my app, I would need to jump ship.</p><h3>All out with Swift</h3><p>I spent the next few weeks learning <a href="https://swift.org/">Swift</a>. I’d started a <a href="https://www.udemy.com/devslopes-ios10/">course on Udemy</a> during a school break, but I never completed it. It turns out that the best way to go through these courses is by having an actual project to work on. As I made my way through the course, I also collected what I thought I would need for my app. Little by little, I saw my app being rebuilt from scratch. What an exciting time! Working with Swift was also quite pleasant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/989/1*YHGTDlu8PdSB_k-1ph8SvQ.gif" /><figcaption>Final Version</figcaption></figure><h4>TestFlight and Beta Testers</h4><p>I’d been talking to a few friends about my little project. I ended up giving 3 of them invites to TestFlight, so they could check it out. Having my app out in the hands of 3 times more people really gave it a chance to break. One weird bug was that the notifications would come at random hours.</p><p>I also got some good feedback from them saying it was very easy to use. One even went on to say that it was better than Apple’s Reminder app because it was so much easier to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OfDGJJ2uifT5RlwKU2J8Jw.png" /><figcaption>Call to action after receiving the reminder. This was a feature suggested by all 3 testers.</figcaption></figure><p>I was very happy with the current state of the app and way more confident than my previous build with Fuse. This time, I actually knew what was going on with my code, unlike with Fuse, where I’d develop in Fuse/Javascript and export it to Xcode and have no idea what was happening.</p><h3>iTunesConnect again</h3><p>I always knew there was a chance that my app could be rejected yet again. My overhaul with Swift made the app much more stable and usable, but I still hadn’t added any other major functionality. It was a tough spot to be. I could try to pivot the app to do some other things (like an AI-based AR experience for receiving reminders), but that would go against the core idea of a quick and easy reminder.</p><p>I submitted it again. It took 2 days for them to get back to me. Maybe it was foolish to think the changes I made would’ve made that much of a difference. I got the same message I had received about a month ago. Binary Rejected — Guideline 4.2 — Design — Minimum Functionality.</p><p>I had the final version of what I wanted my app to be: a painstakingly fast way to set reminders. But it seemed like it wasn’t enough for Apple. They were a lot stricter than I had ever imagined them to be. I still haven’t gotten over the irony of how simplicity was both its main value proposition, but also its biggest shortcoming.</p><p>It was sad to see that, after all this, I would not see my app out in the App Store. It’d been a couple of months of choosing to work on this side project instead of going out or watching Netflix. I was disappointed that all my work had fallen short of my goal.</p><p>I couldn’t stay down forever though.</p><p>I took a step back.</p><p>I realized failures aren’t always complete failures.</p><p>I might have ultimately failed at publishing it to the App Store, but I had also achieved quite a few things:</p><ul><li>I learned how to use Fuse Tools.</li><li>I learned how to develop in Swift.</li><li>I had actually built a product and an experience.</li></ul><p>As basic as they were (it is still just a reminder app), they are things I can carry on. Not only that, but learning and creating something so tangible was an exciting journey in and of itself. Maybe it wasn’t all bad. Maybe it was actually good.</p><p>I guess the main takeaway from this story is that if you stop looking at the outcome and start looking at the process, you’ll find that a little something changed along the way.</p><p>So, I encourage you, who is also passionate about tech, to jump on the bandwagon. Curiosity is innate for us humans. Don’t let it falter. Design, develop, create, build. Make something out of absolutely nothing. You’ll feel good, I swear.</p><p><em>If you liked my story, please remember to 👏 !</em></p><p><em>The app is not available in the App Store, but my friends and I still use it to this day. If you find yourself forgetting to do stuff, please reach out to me and I’ll send you an invite on TestFlight! Additionally, you can also do it at the bottom of the </em><a href="https://kenzonawa.github.io/24do/"><em>landing page</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=600820cf66a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>