<?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 Raphael Cruzeiro on Medium]]></title>
        <description><![CDATA[Stories by Raphael Cruzeiro on Medium]]></description>
        <link>https://medium.com/@raphaelcruzeiro?source=rss-6e0be3f73aeb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8vzNOmuYthEm5t6gkHMI5A.png</url>
            <title>Stories by Raphael Cruzeiro on Medium</title>
            <link>https://medium.com/@raphaelcruzeiro?source=rss-6e0be3f73aeb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:05:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@raphaelcruzeiro/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 we work]]></title>
            <link>https://medium.com/bitdreams/how-we-work-92f925d78121?source=rss-6e0be3f73aeb------2</link>
            <guid isPermaLink="false">https://medium.com/p/92f925d78121</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Raphael Cruzeiro]]></dc:creator>
            <pubDate>Mon, 03 Jul 2017 14:01:56 GMT</pubDate>
            <atom:updated>2017-07-03T20:22:17.137Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OxI_RorEcRMQ9BIWHEb4FA.jpeg" /></figure><p>At Bitdreams we believe that software development lies on the intersection of engineering and craftsmanship. We strive to always improve our craft and deliver top quality products to our clients.</p><h3>Communication</h3><p>Communication is essential for the success of any project. Being tasked with developing software is not just simply putting together a design and programming. We always make sure to understand the business goals of the project, so that we can work <strong>with</strong> the client to design a product that will achieve those goals while also being feasible and within budget.</p><p>We prefer to work with small deliverables, so that we can get constant feedback from our clients, thus making sure that the project meets the client’s expectations and the client is at ease knowing exactly at what stage the project currently is.</p><h3>Quality</h3><p>Whenever we write code, we make sure that not only the finished product looks good and works well but the code is also clear, concise and maintainable. To achieve this, we like to practice <a href="https://en.wikipedia.org/wiki/Behavior-driven_development">BDD</a>. Using the BDD approach for our projects not only ensures the correctness of our code and avoids side-effects introduced by new changes, but also helps us avoid being blocked whenever we need to wait for another party to deliver their part of the project.</p><h3>Network</h3><p>Here at Bitdreams, we like to keep things lean. This means that instead of being like your average software “factory”, we like to keep thing to a minimum and bring people onboard according to the need of our projects. This is only possible because we have accumulated a vast network of trusted people whom we have worked with in the past.</p><h3>We don’t do “one rate fits all”</h3><p>There are several types of projects. From small projects with a clearly defined goal and an beginning and an end to long term projects with requirements that change as the business matures. After understanding what out clients are looking for we can suggest what kind of service they should hire. We sometimes charge a fixed price for the whole project or fixed price for milestone, and sometimes we will sell a monthly pack of project hours when the project is a long term one.</p><h3>We don’t sell “black boxes”</h3><p>We believe that part of our work is to help our clients understand what they bought. We don’t hold source code hostage and we always include a high level documentation of the project. Since we know that often, our clients will grow to the point where they’ll have their own technical team, we are always willing to help them during the transition process (we sometimes even help clients hire their first developers and designers).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92f925d78121" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bitdreams/how-we-work-92f925d78121">How we work</a> was originally published in <a href="https://medium.com/bitdreams">Bitdreams</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From zero to App Store launch in 29 days]]></title>
            <link>https://medium.com/bitdreams/from-zero-to-app-store-launch-in-29-days-91b0f273b01d?source=rss-6e0be3f73aeb------2</link>
            <guid isPermaLink="false">https://medium.com/p/91b0f273b01d</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Raphael Cruzeiro]]></dc:creator>
            <pubDate>Mon, 12 Jun 2017 11:11:35 GMT</pubDate>
            <atom:updated>2017-07-03T20:22:57.253Z</atom:updated>
            <content:encoded><![CDATA[<p>Today we are launching Duomov. Dumov is a simple app that connects two nearby iOS devices and enable them to shoot a dual video. To put it simply: two perspectives of the same place or situation. It uses a peer-to-peer WiFi connection between two devices. All you need is to have WiFi enabled. Being connected to a network or having any kind of Internet connection is not required.</p><p>The idea for Duomov started earlier this year when I hosted a good friend of mine who was traveling through Europe in my apartment in Lisbon. My friend was recording a lot of stuff for his travel journal and we eventually found ourselves recording the same situations. That’s when he said: “Wouldn’t it be cool if there was one app that let both our iPhones record at the same time and then produced a single video with the two perspectives?”.</p><p>Fast forward to May when I finally got the available time to start exploring this idea.</p><h3>Two stage proof of concept</h3><p>It was clear from the start that for this app to work, some sort of communication between the device was going to be needed. I needed to evaluate which kind of communication technology I would be using. Bluetooth was initially considered but discarded before an implementation was even attempted due to the fact that there’s not enough bandwidth to transfer high resolution video through it. I set my sights in figuring out how AirDrop does it.</p><p>Turns out Apple already had a fairly obscure framework called Multipeer Connectivity which seemed to do what I needed. So my first goal was to simply make two iOS devices talk to each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*WBX9outDzk4EUZjNitGTJg.png" /><figcaption>Coding started exactly 29 days before the app was approved by Apple and made available on the App Store</figcaption></figure><p>As it turns out, discovering peers and sending data between devices was a fairly straight forward process. I also tested sending larger data (the size of your average short iPhone recorded video) and everything seemed to be working really well for what I needed.</p><p>The second stage of my proof of concept was having both devices start shooting video at the same time, sending the videos to each other and putting them together in a single video.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F221124278&amp;url=https%3A%2F%2Fvimeo.com%2F221124278&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F639306831_960.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1080" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/21a8c363d639762942cac9283bb4930b/href">https://medium.com/media/21a8c363d639762942cac9283bb4930b/href</a></iframe><p>The final result was a single video composed of the videos recorded on both devices. It was still wildly out of sync but it proved that the concept of the app was feasible for the amount of time that I could allocate to develop it.</p><h3>Turning a proof of concept into a product</h3><p>A product must feel solid, intuitive and has to look good. There’s no arguing that. With that proof of concept in hand, I contacted my friend Pedro Henrique Marques who usually embarks with me on this product development endeavours and he was thrilled by the idea.</p><p>Since we live really far away and are rarely even on the same continent (last time I saw Pedro in person was 4 years ago), we had to really on Trello and Slack for communication and planing. And luckily for us, we are both used to remote work so things couldn’t have gone smoother. We kept in constant touch, exchanging ideas on how the first version of the app should be like.</p><p>As Pedro began working on the designs, I took the time to work on connectivity issues and video synchronization adjustments.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F221124288&amp;url=https%3A%2F%2Fvimeo.com%2F221124288&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F639306838_960.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1080" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/e978818b6e7ccf79fd44cd69b846f5d6/href">https://medium.com/media/e978818b6e7ccf79fd44cd69b846f5d6/href</a></iframe><p>On the very next day, the first designs were ready and the app was also ready for its metamorphosis process. From crude proof of concept to polished product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BxEWZDwSmxpUS5nxbxrvwQ.png" /><figcaption>We used Zeplin so that Pedro could publish his designs for me to implement in code.</figcaption></figure><p>In a couple of days we had the first testable version which we then sent to a few friends who we eager to help us test this app. This was invaluable to help us find a few conceptual problems and bugs early on.</p><p>Our bug count has been kept to a minimal since early on. This is mostly to the fact that our product was well specced and the critical parts were fully tested. Testing not only helped me avoid introducing bugs to our code base, but it also helped me validate assumptions on technology that was then unfamiliar to me such as Multipeer Connectivity.</p><p>In little time our product was already feeling solid. This was really fortunate since Pedro was attending a wedding and took the chance to field test Duomov.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F221203322&amp;url=https%3A%2F%2Fvimeo.com%2F221203322&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F639402196_640.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="720" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/cd3e5a106789b8b34caf0001f2e9921c/href">https://medium.com/media/cd3e5a106789b8b34caf0001f2e9921c/href</a></iframe><p>The main functionality was starting to look good. After yet another a few adjustments to the video merger, we began the final steps for v1: going over all the UI looking for misaligned stuff and localising the app in 7 languages (English, French, German, Japanese, Portuguese, Brazilian Portuguese and Spanish). Again our friends proved invaluable in testing the Gold Master version for us (a special thank you to Igor &amp; Milena Escobar).</p><p>Finally the big day arrived and with a well deserved sense of accomplishment we submitted the the app to Apple.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*ZieNORWcrENnzpYZxZecng.png" /><figcaption>I literally kept checking my phone every 2 minutes thinking I might have missed a notification.</figcaption></figure><p>The review process was fairly smooth. We only had to provide a bit more information to the review team but weren’t asked to make any changes to the app.</p><p>After getting the notification that our app was pending developer release, I exchanged a few short messages with Pedro which went basically like this:</p><p>“Should we wait for our official launch on Monday or should we release now?”</p><p>“What the hell, why not!?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*PQzJKUM4T4QZqUhDTNPtEQ.gif" /><figcaption>And we are a go!</figcaption></figure><p>We are now already working on an update with a bunch of improvements and also writing down ideas for a v2 on our notebooks (Have an idea? Drop us a line!) while at the same time restlessly checking on Fabric to see all these new people trying our app. Overall, the experience of developing Duomov was extremely smooth and fun. We went from absolutely nothing to having a 1.0 version on the App Store in 29 days while also doing other jobs on the side.</p><p>My take on why things went so well? Not being afraid of exploring new technologies and doing thinks differently from previous project, embracing the fact that we need to work remotely and making sure that our both our work and planing are asynchronous.</p><p>You can check more about our app on <a href="https://www.duomov.com/">our website</a> or you can <a href="https://itunes.apple.com/us/app/duomov-make-videos-with-nearby-friends/id1243822610?l=pt&amp;ls=1&amp;mt=8">click here to go straight to the App Store</a>. If you do enjoy Duomov, you can help us by posting the videos you create to you favourite social media outlet with the hashtag <strong>#duomov</strong>, or you can also spread the word to your friends (maybe even acquaintances).</p><p>Looking for a team to turn your idea into an MVP, develop your app, create an awesome design or just looking for the opinion of someone with experience in making ideas reality? You can reach us on <strong>hi@duomov.com</strong> and we’d be happy to discuss things further.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91b0f273b01d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bitdreams/from-zero-to-app-store-launch-in-29-days-91b0f273b01d">From zero to App Store launch in 29 days</a> was originally published in <a href="https://medium.com/bitdreams">Bitdreams</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I prefer code over the Interface Builder]]></title>
            <link>https://medium.com/@raphaelcruzeiro/why-i-prefer-code-over-the-interface-builder-53009eea3ed6?source=rss-6e0be3f73aeb------2</link>
            <guid isPermaLink="false">https://medium.com/p/53009eea3ed6</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[Raphael Cruzeiro]]></dc:creator>
            <pubDate>Mon, 06 Feb 2017 19:54:51 GMT</pubDate>
            <atom:updated>2017-02-06T19:54:51.004Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article was </em><a href="http://raphaelcruzeiro.eu/why-i-prefer-code-over-the-interface-builder/"><em>originally posted on my blog</em></a><em>.</em></p><p>Like many of the iOS (and macOS) developers today, I began developing for Apple devices by following Apple’s own tutorials. I still remember how magical it was, back in 2011 and coming from a background of Python and C++, to open a <em>.xib</em> file and the corresponding class on the assistant editor and just drag from one file to the other to create IBOutlets and IBActions. &#39;This is great&#39;, I thought. It was really refreshing to be relieved of boilerplate code and focus only on what my app should do.</p><p>It didn’t take long though, and I began seeing the downsides of relying on such contraption. Specially when I moved from working on my small educational projects and began working on larger projects with other developers.</p><h4>Merging hell</h4><p>Both <em>.xib</em> and <em>Storyboards</em> are not meant to be human readable. You are supposed to work with the nice graphical representation of those files that Xcode generates for you. This means that if you and your coworker happen to be doing work on the same file, one of you will have to deal with solving merge conflicts later on. A lot of the times, merging will involve choosing changes randomly and then opening the file on Xcode and figuring out what needs to be done to ensure that the file is in the state it needs to be.</p><p>Last but not least: Xcode will alter the Interface Builder files just by opening them. Sometimes the slightest modification results in massive changes to the file (this is because the <em>XML</em> nodes of the file are represented as a <em>set</em> in memory and sets do not guarantee order). Other times Xcode will just change the syntax of the <em>.xib</em> for the fun of it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YfztghugTr7GdGf5FIb35g.png" /><figcaption>Auto generated change that doesn’t add anything to the project besides probably migrating to a new IB schema</figcaption></figure><h4>Tight coupling with (almost) no compile time safety</h4><p>Have you ever ran your app, with confidence that it would work as expected, just to see it crash once you open a certain view controller? And upon checking what exactly the crash was, figured that it was an IBOutlet that was not connected? Yeah, we’ve all been there.</p><p>Moreover, Interface Builder files are harder to reuse and even harder to refactor. It’s almost impossible to get a single look at a file like that and have a good idea of everything that that file is defining.</p><p>I’ve seen just about everything when it comes to Interface Builder woes. From files that would suddenly make Xcode crash just from opening a certain file to a view controller that could be instantiated with different <em>xibs</em> and when instantiated with one of these <em>xibs</em> could lead to a crash because, wait for it, an IBOutlet didn&#39;t have the correspondent element on that <em>xib</em> and since Xcode generates the IBOutlets as <strong>implicitly unwrapped optionals</strong>, any attempt to access that variable would cause the app to crash.</p><h4>Dragging and clicking things is not my strong suit</h4><p>There are small things that make the task of adding a constraint through the Interface Builder an infuriating task. Like having to move to the next layout constraint field so that Xcode will not ignore my constraint when I click <em>Add Constraint</em>, the time it takes for Xcode to open a single Storyboard, or being in the middle of editing something and having Xcode crash on me (and then having to reopen the project and figure out what was the last change that got saved).</p><p>When UI work is done with code, it’s easier to figure out exactly what is happening or what do I need to change in that code that was written one year ago to implement that new feature. Specially if the code was written with consideration for good practises, everything will be explicit and I will know exactly where to look. This is something that reminds me of the joys of the years I spent working with Python: <a href="https://www.python.org/dev/peps/pep-0020/#id3">Explicit is better than implicit</a>.</p><h4>But writing auto layout code is so verbose and tedious…</h4><p>There are a few frameworks that take away the pain of writing auto layout code. My framework of choice is <a href="https://github.com/robb/Cartography/">Cartography</a>. Cartography makes writing auto layout code extremely simple and intuitive. Just check out this example from the project’s README:</p><pre>constrain(view) { view in  <br>    view.width  == 100<br>    view.height == 100<br>}<br><br>let group = ConstraintGroup()<br><br>// Attach `view` to the top left corner of its superview<br>constrain(view, replace: group) { view in  <br>    view.top  == view.superview!.top<br>    view.left == view.superview!.left<br>}<br><br>/* Later */<br><br>// Move the view to the bottom right corner of its superview<br>constrain(view, replace: group) { view in  <br>    view.bottom == view.superview!.bottom<br>    view.right  == view.superview!.right<br>}<br><br>UIView.animateWithDuration(0.5, animations: view.layoutIfNeeded)</pre><p>It can&#39;t get any simpler than that. Plus, it&#39;s always a joy to be able to see and quickly understand everything my coworker did during a code review:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TJlQikv2gCxgs8w2_Axwmw.png" /><figcaption>You can easily understand what has been changed just by a quick glance</figcaption></figure><p>Did you see that? Constants! Sweet constants!</p><p>There will always be those cases that you feel at a loss on how to implement something with auto layout. For those cases I can tell you this: there’s nothing wrong with overriding layoutSubviews and calculating your frames there. Don&#39;t ever let someone tell you otherwise. Always favor the simplest solution to a problem.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53009eea3ed6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>