<?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 Deja Jackson on Medium]]></title>
        <description><![CDATA[Stories by Deja Jackson on Medium]]></description>
        <link>https://medium.com/@bananafudgkins?source=rss-2b1c969fa68------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2F2GtlXzxyfeTCyXkl4I9A.jpeg</url>
            <title>Stories by Deja Jackson on Medium</title>
            <link>https://medium.com/@bananafudgkins?source=rss-2b1c969fa68------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:37:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bananafudgkins/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[iOS 10’s Speech Recognition API]]></title>
            <link>https://medium.com/@bananafudgkins/ios-10s-speech-recognition-api-17e801a4f81?source=rss-2b1c969fa68------2</link>
            <guid isPermaLink="false">https://medium.com/p/17e801a4f81</guid>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[xcode]]></category>
            <dc:creator><![CDATA[Deja Jackson]]></dc:creator>
            <pubDate>Wed, 24 Aug 2016 06:43:34 GMT</pubDate>
            <atom:updated>2016-08-24T06:43:34.795Z</atom:updated>
            <content:encoded><![CDATA[<p>Let me just start by saying that iOS 10’s new native speech recognition API is a long-awaited technology. Developers can now use the same service that powers dictation in Apple’s first party apps. However, like most new APIs introduced, it’s a pain in the ass to implement. This is mainly because you not only have to deal with the Speech framework, but AVFoundation as well. Please note that what I’m about to discuss is about the live audio portion of the API, not when the API is used to process speech from a pre-recorded audio file.</p><p>Setting up the API is a multi-step process. You first must create an instance of the SFSpeechRecognizer class. This class is the main hub for everything speech recognition on iOS. You must specialize a locale for the recognizer to recognize. Most developers may go with American English (the language I’m currently writing this article in). The NSLocale code for American English is “en-US.” However, the great thing about the speech recognized class is that it can use whatever locale the current device is set to use.</p><p>Whelp it’s been a little while since I was last writing this draft. After some experience, I can say that while setting up the speech framework is not the most reliable process, it can be very simple once you have the right methods in place. For example, my app Voicepedia, an app that allows you to search Wikipedia using only your voice, was originally using a third party service called Nuance for speech recognition. With the Xcode 8 beta now out, I decided to upgrade the app to iOS 10&#39;s native speech recognition API. Because there are multiple steps to finding a Wikipedia article within the app, speech is processed by the app a lot. I first tried just replicating the iOS 9 and earlier code I had but using the speech API instead of Nuance. While the recognition would work once or twice, it was a very unreliable process that could crash at any moment. This was mainly because in order to begin speech recognition you must first install an audio tap on one of iOS’s audio busses. The main problem was that the audio tap would not always be removed from a bus (even though I would explicitly call the method to remove one) which would in turn cause the app to crash. This is because an audio bus can only have a single audio tap on it.</p><p>With this rewrite I decided to have all the speech be handled by a delegate method rather than having the speech be processed directly by a result handler. By calling on a delegate function this also meant that I would have to write less code. Each time the user was to be prompted to speak, I would call a method that would set up the speech recognizer. From there a delegate method would be called when a result was generated. This delegate method was where I did the actual speech processing.</p><p>In conclusion, it seems that using delegate methods is the best way to go if you are using speech recognition multiple times and if there is a small gap of time between those uses. I first started by making a method that would be called each time the app needed to set up speech recognition. This meant I could call the same block of code each time for a certain task. I won’t type any actual code here ( I don’t want anyone stealing my source code) but I hope you’ve at least learned a little about how the new speech API works.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17e801a4f81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yet Another Update]]></title>
            <link>https://medium.com/@bananafudgkins/yet-another-update-86c642fec4de?source=rss-2b1c969fa68------2</link>
            <guid isPermaLink="false">https://medium.com/p/86c642fec4de</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Deja Jackson]]></dc:creator>
            <pubDate>Thu, 04 Aug 2016 01:11:59 GMT</pubDate>
            <atom:updated>2016-08-04T01:11:59.481Z</atom:updated>
            <content:encoded><![CDATA[<p>So I’ve been working with the Xcode 8 beta to get Blooom ready for iOS 10. The funny thing is I currently don’t have a version that’s made for the currently released version of iOS. The weird thing about Xcode 8 has been just how buggy the Swift compiler is. Luckily cleaning the project a few times got rid of the 34 errors that I didn’t even understand. Hopefully I’ll have Blooom ready within the month. If development continues at its current pace, Blooom will probably be launching close to late August or early September. Also shoutout to all 2 of my followers for supporting me during this app’s development. You both have really made a difference in my life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86c642fec4de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Update on Blooom’s Development]]></title>
            <link>https://medium.com/@bananafudgkins/hey-just-thought-id-update-everyone-about-the-status-of-blooom-yes-i-m-still-calling-it-that-97581ae7e75?source=rss-2b1c969fa68------2</link>
            <guid isPermaLink="false">https://medium.com/p/97581ae7e75</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Deja Jackson]]></dc:creator>
            <pubDate>Sat, 23 Jul 2016 00:01:07 GMT</pubDate>
            <atom:updated>2016-07-23T00:06:43.290Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey just thought I’d update everyone about the status of Blooom (yes, I’m still calling it that). I haven’t done much on it lately and development has really slowed at this point. I did recently get push notifications working with Apple’s CloudKit service (I’m slowly but surely learning the API) since the service I previously used, Parse, is being shut down. The main reason why development has been so slow is because of the fact that I’m using a completely new technology to power the app and am dealing with an API I’ve never used before. Hopefully I’ll be able to finish the app soon but don’t get your hopes up.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97581ae7e75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working on a New App]]></title>
            <link>https://medium.com/@bananafudgkins/working-on-a-new-app-b26a6245ad3c?source=rss-2b1c969fa68------2</link>
            <guid isPermaLink="false">https://medium.com/p/b26a6245ad3c</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[live-photos]]></category>
            <category><![CDATA[ideas]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Deja Jackson]]></dc:creator>
            <pubDate>Wed, 15 Jun 2016 00:58:46 GMT</pubDate>
            <atom:updated>2016-06-15T00:58:46.940Z</atom:updated>
            <content:encoded><![CDATA[<p>So after the crisis I had with Song Sync’s development and after stopping development on the next idea after that, I’ve settled on another new idea. I’m hoping to create the first iOS social network that uses Apple’s new Live Photos technology. I just thought of the idea today after watching a WWDC session about iOS 10’s new photography enhancements. I’ve decided to name it Blooom (the name Bloom is already taken on the App Store). Hopefully this idea will be successful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b26a6245ad3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to the Drawing Board]]></title>
            <link>https://medium.com/@bananafudgkins/back-to-the-drawing-board-eaefd23df531?source=rss-2b1c969fa68------2</link>
            <guid isPermaLink="false">https://medium.com/p/eaefd23df531</guid>
            <category><![CDATA[app-idea]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Deja Jackson]]></dc:creator>
            <pubDate>Mon, 18 Apr 2016 17:44:19 GMT</pubDate>
            <atom:updated>2016-04-18T17:47:18.101Z</atom:updated>
            <content:encoded><![CDATA[<p>So… I was working on an app called Song Sync which was supposed to be an app where people could connect to DJ rooms and listen to the same music as whoever was running the room.</p><p>Here are a few screenshots of the progress I had made:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*xSNchEBTXe6ilBijMHU-2Q.png" /><figcaption>The interface showing you what rooms you could join</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*L__rTbMC3YgXSwb_bVktKA.png" /><figcaption>The dialog that would show you information about that room</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*X5Wh19sDVqCnxGqi89XE9g.png" /><figcaption>The interface for creating a new room</figcaption></figure><p>So… if this intrigues any of you it was something that I was working on in my spare time but then I realized that the APIs for the various services I wanted this app to use weren’t built for the purpose of having a bunch of people listening to the same song at the same time. So, due to these technical barriers, I’ve decided to abandon development on this app and move on to make a new one. Maybe I might start working on a messenger or something…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eaefd23df531" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>