<?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 David West on Medium]]></title>
        <description><![CDATA[Stories by David West on Medium]]></description>
        <link>https://medium.com/@david_west?source=rss-94d4ef5c2af7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*j1vByirP3J9UQG68.png</url>
            <title>Stories by David West on Medium</title>
            <link>https://medium.com/@david_west?source=rss-94d4ef5c2af7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:25:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@david_west/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[DEVELOPER DIARIES: How NOT to launch your new app…]]></title>
            <link>https://medium.com/@david_west/developer-diaries-how-not-to-launch-your-new-app-7c33554c878b?source=rss-94d4ef5c2af7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c33554c878b</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[David West]]></dc:creator>
            <pubDate>Sun, 25 Sep 2016 12:14:36 GMT</pubDate>
            <atom:updated>2016-09-25T12:14:36.444Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x-TUrkdux2A4F0USz9PHwg.png" /><figcaption>The Positve &amp; Negative attributes acquired from iOS App Development</figcaption></figure><p>There are some common misconceptions about the creation of apps. The main two I’ve stumbled across include that <strong>a) they aren’t that costly</strong> to create and <strong>b) that they are actually fairly easy</strong> to get on to the app store. I will be addressing misconception ‘A’ in a future post, but for now I wanted to share the far from easy first experience of submitting <a href="http://www.scorelord.co/"><strong>ScoreLord Tennis</strong></a>, my first app, on to the AppStore. This submission will be done in diary-form.</p><p>I have also created some <a href="https://medium.com/@davidrwest/intriguing-insights-the-apple-app-review-process-7667785f31b4#.84gngc9ia"><strong>interesting insights into the submission process over here</strong></a>, if you are craving a more mature write-up. There I go into who was reviewing the app, how quickly they were doing so &amp; how the review process could be improved by Apple.</p><p>Here, I will childishly document everything that went wrong, each and every single day…</p><p>Hopefully, as a reader, you will take something valuable from this, whether it be <strong>1) avoiding these foolish mistakes, 2) factoring-in extra time to iron-out issues or at least 3) enjoying a good-old laugh at my expense</strong>.</p><blockquote><em>“If you can survive an app release, you can survive anything” </em><a href="https://medium.com/u/8f8d192cb8c7"><em>Andreas Kambanis</em></a><em>, 2016</em></blockquote><p>One of my close friends was quoted as saying this earlier this year. I laughed &amp; brushed it off at the time. Now, I can totally empathise with it. By reading on about the nightmare that was my first ever submission to the AppStore, you may too…</p><h3>30th August</h3><ul><li>08:15 — Tuesday 30th August was submission day and it was a productive day spent in Xcode, an early start (for a dev). However there were far more last minute code tweaks &amp; changes than I had anticipated and so both myself and my trusty senior developer turned out to have quite a long day in front of our screens. That’s all good though, today was the final day of what had been 12 months of development, or so I told myself…</li><li><strong>No one likes Dates, not even of the dried food variety</strong>. Well, at least developers hate dates. Anyone that has done any coding will appreciate that dates are a massive pain in the bee-hind. Localising them to each and every user can be a long process. Yep, it sucks.</li><li>20:15 — When I was almost ready to submit, it struck me that we hadn’t localised the dates in the app for tennis match invitations (not a big issue for UK and European users but certainly so for users in the US). Players just miles from each other could be sitting in separate time zones and seeing invitations for different time zones — d’oh, this needed fixing!. I suspect many of you developers have had similar Homer Simpson moments in your early years and can now relate to that quote we saw earlier.</li><li>23.15 — Fixed the date issue &amp; generated distribution certificates (also a painful process). Then whilst I was creating the archive (which you upload to the AppStore as a .ipa file) I gave my seasoned developer veteran the green light to head to bed. I had this covered I said to him, I’ve just got to press upload. Or so I thought…</li></ul><blockquote><strong>DON’T USE BETA OPERATING SYSTEMS</strong></blockquote><ul><li>01:00 — Shortly after submission, I was promptly made aware that my build was not compatible &amp; that by running a beta version of Mac Sierra, with a non-beta version of Xcode 7, I was unable to publish my app to the AppStore. Frantic Googling followed to find the best solution…</li><li>01:30 — Found the “best” solution which entailed modifying the SystemVersion.plist file &amp; representing an earlier version. Not ideal but better than rebuilding the OS. For now.</li><li>02:00 — Locked-down my computer having restarted when I should not have done, rendering all of my Mac apps useless &amp; incompatible, including TextEdit &amp; more critically…Terminal which were needed to modify the file back. My computer was crying inside, as was I. Panic followed. I was so close to an anxiety attack…</li><li>03:30 — Found a way to go into Single-User mode on boot-up of my Macbook to modify-back the Plist file. Restarted and was back to square one. 2 hours, still a nervous wreck, zero progress, but zero lost.</li><li>04:00 — By this time, I had managed to make the change effectively and was now waiting for 4GB of Xcode 8 to download, so I could upload using its Application Loader. Thumbs-up for shizzy slow internet!</li><li>07:00 — After a successful install &amp; archiving the build once more, I was able to submit my second non-beta version to the AppStore, but I was greeted by yet another error message. I had forgotten to change the build number of my previous build. D’oh, again! Despite the previous build being auto-rejected, it had still caught and registered it within iTunes Connect so a new reference was required. Soon, I was repeating the previous 60 minute process once more, setting the build number to ‘2’, instead of ‘1’.</li><li>09:15 — Somehow during this re-run the build had changed to ‘Universal’ and I was greeted with yet another issue….missing App Icons — for iPad. I wasn’t even supporting iPad and never had, but by quickly changing the build back to ‘iPhone’…my brain was subjected to another 60 minute struggle staying awake.</li><li><strong>10.45 on 31st August — FINALLY uploaded &amp; submitted. It’s all plain sailing now, right!?</strong></li></ul><blockquote><strong>Lesson #1: Never install beta OS on your main mac or computer. It’s just totally not worth the pain! Not unless you too fancy a sleepless night… #noob</strong></blockquote><h3>31st August (still same day but felt like a new one)</h3><ul><li>11.15— Finally got to sleep’ish.</li><li>13:00— Quickly woke up to the feeling of relief but also of “what do I do now?” syndrome. I headed over to go see and entertain my nephew for a few hours, whilst in an energetic (“I feel like I have had 10 hours sleep”) mode.</li><li>18.00 — Evening strikes &amp; 13 hours of pure unadulterated, uninterrupted sleep follows. Bliss!</li></ul><blockquote><strong>Lesson #2: For your first ever submission, try and line up something to do for the day, rather than self-inflicting “F5 Refreshing Hyperactivity Disorder” (FRHD) on yourself, expecting the status of your submission to change. Being accompanied by an 8 month old terror for the afternoon was all that I needed to release my mind from this insanity.</strong></blockquote><h3>1st September</h3><ul><li>13:30 — Whilst seeing that the app was in “<strong>Waiting for Review</strong>”, I could see Apple had been accessing and testing the app in Cupertino, creating a new account &amp; interacting with matches. This was visible using the Analytics solution I had integrated as part of my project. Interesting to see that in all honesty, I was expecting them to begin testing whilst the app was ‘In Review’.</li><li>18:22pm — App officially goes into “In Review” — that was quick!</li><li>Thoughts were that maybe I could release it this week, after all. So I best tell everyone…tomorrow is the day!</li></ul><blockquote><strong>Lesson #3: MISTAKE. Don’t expect to succeed on your first ever submission…and certainly don’t embarrass yourself by saying your app will be available the following day, when it is still subject to the review process. I’m sure plenty of people were confused when they could not find my app on the store the following morning, after reading my “heads up” email. #EmailFail</strong></blockquote><h3>2nd September</h3><ul><li>05:50 — Received the notification every one of us dread “<strong>App Rejected</strong>”. Reason being that I was requesting personal identifiable data as mandatory. Apparently personal identifiable data cannot be deemed so, certainly not if it is deemed irrelevant. I felt it was relevant in this instance, being a sports social app seeking to pair similar players of similar age &amp; gender. So I drafted a polite response to that effect.</li><li>09:30 — Later submitted a clarification mail detailing why DOB &amp; Gender are mandatory fields on sign-up, reiterating the dependency on pairing with nearby players &amp; also that users can bypass the registration process altogether (and access limited parts of the app) if they desire.</li><li>10:30 — Followed-up with a second mail, attaching screenshots, showing tens of examples in the social-sports category which force similar information on Sign-Up. In the previous few weeks, I could see that the examples I provided of other apps, showed that they had recently made their way through approval without any issue whatsoever.</li><li>However, I opted to bite the bullet &amp; address the issue. I figured my chances of getting someone from Apple to admit that they were wrong were pretty slim. So I took the opportunity to address some other performance related bugs I had noticed, and made the Date of Birth field an optional entry. Boom, resubmit!</li><li>22:43— New build submitted. I also figured no-one downloading a Sports-Social app is protective over their Gender… right? This could stay as it was, I told myself, and gave Apple my ‘justification’.</li></ul><blockquote><strong>Lesson #4: Be polite when interacting with the review team over rejections. I can whole-heartedly say that I was. Whilst it got me nowhere quickly… I did also choose to flag-up &amp; screenshot other apps that had similar sign-up processes. Probably best to not do this…as you’ll see in the period that followed… #Silence.</strong></blockquote><h4>3rd September</h4><ul><li>Nothing</li></ul><h4>4th September</h4><ul><li>Nothing</li></ul><h4>5th September</h4><ul><li>Surprise surprise… nothing!</li><li>Thankfully, today I was travelling down to <strong>iOSDevUK</strong> in Wales where I would be mixing with some fellow geeks, at my first dev meetup / conference since opting to teach myself to code 12 months ago.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sXHla_jQkOsrGldCCEVq7g.png" /><figcaption><a href="https://medium.com/u/94d4ef5c2af7">David West</a> @ iOSDevUK</figcaption></figure><ul><li>This was actually a fantastic distraction, &amp; over the course of the next few days I would get to mix with some fantastic peeps. My favourite talk was given on the 3rd day by <a href="https://medium.com/u/653fd6c70de0">Richard Turton</a>, titled “I’m an Idiot”, something I found very simple to relate to. I wonder why!</li></ul><blockquote><strong>Lesson #5: Surround yourself with other developers when waiting for review. Hearing their similar stories &amp; having someone to share your story with (especially someone who won’t go cross-eyed when discussing the process)… will keep you sane, initially at least.</strong></blockquote><h4>6th September</h4><ul><li>Nothing</li><li>Maybe with the apple event looming, the review team were catching up on holiday before the inevitable rush of iOS10 &amp; Sticker App submissions. Maybe…</li></ul><blockquote><strong>Lesson #6: Keep busy.. take a holiday, get involved with some prototyping, anything to occupy your mind. #Patience!</strong></blockquote><h4>7th September</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jTdWnE4dM4d4RRyKCdXtcg.jpeg" /><figcaption>Apple Event streamed @ iOSDevUK</figcaption></figure><ul><li>Nothing</li><li>But hey… the Apple event was here. You’ve never watched an Apple event properly until you’ve been sat in a lecture theatre with hundreds of cynical developers! #Courage</li></ul><h4>8th September</h4><ul><li>Nothing</li><li>Morale at an all-time low.</li></ul><blockquote><strong>Lesson 7: Definitely best not to highlight inconsistencies with the Apple Review process or waste time challenging decisions. Whether it impeded me or not, it certainly didn’t help. I was still waiting!</strong></blockquote><h4>9th September</h4><ul><li>02:18— Wake up to ‘In Review’ and ‘App Rejected’ within several hours of each other.</li><li>13:37 — Begrudgingly, submit another build addressing every one of the Apple Review team’s concerns, abandoning my dignity in favour of securing approval.</li></ul><blockquote><strong>Lesson #8: Not sure that Apple “negotiate” with developers. I’d advise if they ask you to make any change(s), to just make them. Regardless of whether you believe them to be right or wrong. If you don’t, expect a long and painful week or so… before a likely rejection email. #Hindsight</strong></blockquote><h4>10th September</h4><ul><li>Nothing</li></ul><h4>11th September</h4><ul><li>Nothing (do testers actually work on weekends?)</li></ul><h4>12th September</h4><ul><li>Nothing</li></ul><h4>13th Septmeber</h4><ul><li>Nothing</li></ul><h4>14th September</h4><ul><li>21:15 — Ooeeee app status changes to “<strong>In Review</strong>”</li><li>Sleepless night follows</li></ul><h4>15th September</h4><ul><li>04:10 — App “<strong>Pending Developer Release</strong>”</li><li>23:10 — YESSS, <strong>APPROVED</strong>!!! Bingo, bingo, bango.</li><li>Prepped my contact who would feature me at <a href="https://www.producthunt.com/tech/scorelord-tennis"><strong>ProductHunt</strong></a> &amp; provided links, images etc for publication the very next day.</li><li>More sleep follows.</li></ul><h3>THE END.</h3><p>Or not…</p><h4>16th September</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*OdLzu4xlhzg_tAeFNDc6bQ.jpeg" /></figure><ul><li>01:00 — Except that wasn’t the end or time to sleep. I found a couple of <strong>CRITICAL BUGS</strong> after I had submitted &amp; set status to “Ready For Sale”.</li><li>With the decision to launch with a buggy app or let my email subscribers down once more, I opted for the more risqué option. <strong>Save face &amp; Launch! </strong>I’d then submit a new update instantly.</li><li>03:00 — Started a new build, fixed 80% of issues, and requested priority status from Apple before I put my sensible pyjamas on. Went to sleep, without submitting. I’m becoming sensible now…</li><li>09:00 — Woke up early to check whether listed on ProductHunt. F5, F5, F5, F5, F5, F5…etc until 11:30. D’oh, we had been forgotten!</li><li>11:45 — It was time to postpone launch on PH until the following week &amp; complete the update before the peeps in California wake up.</li><li>17:28 — Fixed bugs &amp; submitted new build. V1.0.1.</li><li>18:24 — In Review — WOW that was quick!</li><li>21:00 — <strong>Rejected</strong> — OH NOOOOO NOT AGAIN!</li><li>Rejected for the very same functionality that I addressed for the review team in V1.0. This was infuriating &amp; I opted to involve the “<strong>App Review Board</strong>” this time to challenge the decision!</li><li>23:03 — Made more changes &amp; beyond any reasonable doubt ensured the same issue would not arise — removing validation on signup fields. <strong>SUBMISSION 127,437 or so it felt</strong>.</li></ul><h4>17th September</h4><ul><li>Some great detailed dialogue followed with the App Review Board, whereby they presented some additional concerns. Clearly &amp; concisely.</li><li>Recognising this was an important bug fix though, they agreed to approve on the basis that I submitted another build in a months time…which addressed the one remaining aspect of the app that was borderline adhering to their guidelines.</li><li>21:29 — I’d had success in getting Apple to be flexible &amp; considerate. Maybe now I could call myself a seasoned developer I asked myself?</li><li>21:55 — Update V1.0.1 — Released and set to “<strong>Ready For Sale</strong>” and now I could rest easy, knowing the app was stable, functional &amp; working as intended originally. What a weight off my shoulders! If only we had been here 3 weeks ago when I started capturing this process.</li></ul><h4>18th September</h4><ul><li>Sunday — The Day of Rest…. and…the day of preparing your app for an official launch! Well, for me at least.</li></ul><h4>19th September</h4><ul><li>07:40 — Wake to the sight of my app on <a href="https://www.producthunt.com/tech/scorelord-tennis"><strong>ProductHunt</strong></a> and gleaming in all of its glory! Wooooop.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GgiHKK3XCj77YpwnxH7IpQ.png" /></figure><blockquote><strong>Lesson #9: Be patient, resilient &amp; don’t lose your cool. I’m sure none of you have had such a horror of a time launching your first app like you see above. However we all have our problems getting applications over the line &amp; it’s very easily (I found) to take it personally &amp; get frustrated. However I found solace in knowing that I WOULD SUCCEED eventually &amp; that this was a learning experience.</strong></blockquote><blockquote><strong>I had come THIS far now, what was another few days or hours…particularly on a project that has been 13 months in the making?</strong></blockquote><p>What happened next you want to know? How many page visit, downloads etc from the launch? What did I do for marketing? Well, I’ll save all of that juicy stuff for another post… so stay tuned &amp; <strong>click the follow button</strong> to catch my next post.</p><h3>THE. ACTUAL. END.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c33554c878b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WWDC : What Weren’t Developers Contemplating…]]></title>
            <link>https://medium.com/@david_west/wwdc-what-werent-developers-contemplating-7f611ae563ad?source=rss-94d4ef5c2af7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f611ae563ad</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[David West]]></dc:creator>
            <pubDate>Thu, 02 Jun 2016 12:42:01 GMT</pubDate>
            <atom:updated>2018-06-19T23:04:16.292Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/807/1*0sF8tos8Q_DQSnFKZ7SVlw.jpeg" /></figure><p>When Apple announced WWDC on 18th April people were questioning whether it was a mistake or a case of butterfingers by Apple. <strong>News broke via Siri</strong>. Siri? What does she know? MUST have been a mistake, right?</p><p>With it, came the following poem:</p><blockquote>- Hello love at first swipe ….…………..TINDER?</blockquote><blockquote>- Hello other side of the road …………CROSSY ROAD?</blockquote><blockquote>- Hello yogi on my wrist ………………POCKET YOGA?</blockquote><blockquote>- Hello driver, fast as you can …………UBER?</blockquote><blockquote>- Hello workout in my living room ……7 MINUTE WORKOUT?</blockquote><blockquote>- Hello every pitch, every highlight …..MASTER LEAGUE BASEBALL?</blockquote><blockquote>- Hello self-combusting selfies …………SNAPCHAT?</blockquote><blockquote>- Hello double tap heart ………………INSTAGRAM?</blockquote><blockquote>- Hello rain in five minutes …………..DARK SKY?</blockquote><blockquote>- Hello 6 minutes of fame …………….VINE?</blockquote><blockquote>- Hello big idea ………………………..Mac OS11?</blockquote><p>…all could potentially indicate voice recognition &amp; integration into the above apps &amp; OS (belatedly)? My wishful mind has got me thinking…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LJMXSNN4CuGPoum_pg1N8g.png" /><figcaption>So why has no one else been talking about Siri until now?</figcaption></figure><h3>App-uisitions</h3><p>Apple has also been busy acquiring new companies in recent years with last years purchase of <a href="http://9to5mac.com/2015/10/02/apple-vocaliq-acquisition/">VocalIQ</a> particularly interesting, as mentioned by <a href="https://medium.com/u/7236cb540a10">Brian Roemmele</a> <a href="https://medium.com/@brianroemmele/has-apple-lost-its-way-with-ai-cde76172a630#.c5p610jrd">here</a>. Siri has not just needed an injection of new AI but has been fundamentally flawed the way ‘she’ was designed.</p><p><em>Siri has a low IQ and is comparable to a parrot, repeating what it is told and (often, frustratingly) responding imprecisely.</em></p><p>Everything she’s been taught has needed to be hard-coded in. What this acquisition of VocalIQ seems to suggest is that Apple has now the capability to replicate what the team at <a href="http://www.macworld.com/article/3067407/ios/meet-viv-the-new-voice-assistant-from-the-creators-of-siri.html">Viv recently announced</a>, which is an AI voice recognition system that grows and learns and becomes better the more people use it and the more developers adopt it.</p><p>Even if the product can only offer slight learning capabilities; no rivals can rival Apple’s device adoption &amp; coverage right now &amp; so despite Apple being relatively late to the game and having been behind the competition to date (*cough* <strong>Siri hasn’t been updated on iPhone in 4 years</strong>), they could scale the development &amp; intelligence of their voice platform EXTREMELY quickly. This would add fuel to the fire and justify why Apple, a typically closed company, would go open-source on any API.</p><p>News then broke last week that <a href="http://www.theverge.com/2016/5/24/11763836/apple-siri-speaker-amazon-echo-alexa-google-home-ai">Apple is working on an Amazon Echo / Google Home competitor</a>. “Inside” sources mentioned Apple shipping a brand new product with the Siri SDK to share with the world at WWDC. Others, suggested that product would come later.</p><p>I believe that to be completely false though. Apple devices are already some of the most adopted in the industry and to release a new ‘AI Assistant’ box with no purpose besides sitting still on the bookshelf in the living room (when the value is in the software) would signify a HUGE waste of Apple’s R&amp;D budget. Especially when Watches remain on our wrists, TV units stay fixed in the room &amp; phones get carried in our pockets wherever we go. Speaker included or not… what is far more likely is that the supercharged technology gets wrapped into <strong>Watch OS2, Apple TV OS10, Mac OS11</strong> and so we see upgraded hardware &amp; software for Apple TV and Mac and Watch.<strong> It’s been 4 years Steve since we last saw Siri smile</strong>, so we’ll take that!</p><p>This news and thinking has gained a lot of coverage inside The Verge, Mashable, Wired, 9 to 5 Mac etc etc etc…but what many have failed to contextualise is the impact that this would have on the whole of Apple’s product portfolio. Christmas could come early…</p><h3>This Will be The Biggest EVER WWDC</h3><p>So what would Voice Recognition bring to each device? Is it <em>THAT</em> significant?</p><h4>Apple iPhone</h4><p>Specific contextual conversations with your phone about when will the next tube or bus arrive or “when do I need to leave the house today for work?”, “how much would Uber cost to take me to Ikea?”, “next exercise please Siri” would transform overnight the way people interact with the most sought-after devices in the world and their most popular apps.</p><p>Going from navigating amongst &amp; organising hundreds of apps, to having one single input to call upon and dive directly into timely information..would negate the need for deep navigation controllers.</p><p>Better still….being able to drill down and filter that information based upon further inputs &amp; context….you can begin to see how that would be big…can’t you??</p><p>No? You wouldn’t talk to your phone on the train to work?</p><h4>Apple Watch</h4><p>Ok well for Watch, voice upgrades would change the game &amp; transform its fortunes overnight. Especially when combined with the inevitable hardware &amp; software upgrades that Apple’s “flop” will receive.</p><blockquote>We’d see a stampede of Weys rather than Mehs. Haters would become maters &amp; owners would become loners…resorting to Siri for their daily ‘social’ interaction.</blockquote><p>Rhymes aside, it would without doubt suddenly make the Apple Watch the product it should always have been. Glances and Complications have attempted to address the biggest problem with the Apple Watch, a lack of interactivity &amp; short attention spans. There are hundreds of cynics who have got nothing back from an Apple Watch besides an expensive timepiece. And millions more WANT to be told it is a masterpiece to justify jumping in &amp; spending more big bucks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*XrLt7UMbN4xg0hUkgz4HkA.png" /></figure><p>Extending Siri would mean just that and would make navigating through via the Watch Home screen completely unnecessary.</p><p>Something so simple as “Siri, ring my phone. I’ve lost it” would scratch a big itch with owners.</p><p>“Siri, I’m going for a run” would shock her to the core, but would open up Strava.</p><p>“Siri, tell me what’s the next step for this recipe” in <a href="https://medium.com/u/340f14cee272">FitMenCook™ (Kevin)</a>.</p><p>This could all be achieved without Siri ever attempting to use Google, her current &amp; default defence mechanism. And yes this is what Siri SHOULD be like, but it has to be this way. If Siri for TVOS is replicated on Watch and requires wearers to dictate “Launch Strava”, “Launch Find My iPhone”…well perhaps we can forget about Siri for another 12 months. That would probably still be far too obtrusive.</p><p>That said, allowing users the freedom to choose their default apps for specific commands or create their own commands would be too much complication for them too. I would expect custom commands (such as those mentioned above) to feature and to be called from the background. Then any conflicts to be presented to the user. It would be far more convenient &amp; natural than requesting to launch an app.</p><p>My guess would also be that the side button which takes you to the Watch’s contacts app, would become Siri’s trigger on the Watch. The Watch has always suffered and been compromised by its appalling battery performance. And whilst with the iPhone I suspect will always be “listening” for Siri’s name (plugged in or not this time around), the Watch is compromised much more in terms of performance.</p><h4>Apple TV</h4><p>Apple sold us a dream last year when Apple TV was portrayed to be intelligent to filter shows &amp; movies based on new criteria. It did well initially to capture people’s imagination by being able to command “turn on subtitles”, “show me only movies by Jack Black &amp; only the new ones”, “play season 2, episode 1” and more impressively “what did they say?” (to go back and rewind) or “launch Photos” (to open other TV OS apps).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*Cu3Ymt1uA-Kg5ZxF56Hm_g.jpeg" /></figure><p>However this never felt like Siri had changed her architecture and if she had (Siri the parrot) was still certainly being kept in a cage…to see how users interact with her.</p><p>Users are still unable to say “buy” or “rent” when navigating through shows, add songs to playlists, search for Apps in the AppStore or more impressively cater content based on the voice that she hears (something crucial given todays different tastes in TV).</p><h4>Apple CarPlay</h4><p>Whilst Siri is said to perform better on four wheels, due to the confined space…truly handsfree driving is way off. Yes Apple is working on a Tesla replacement, but we don’t care about this today. Apple are years away.</p><p>When using Siri in the car today, users still have to touch results on screen to navigate through them. It hasn’t felt like a hands-free experience and so cars are crying-out for a context-conscious version of Siri. Hopefully too, she would be listening for her name rather than having to press a button on the wheel (if your car is fitted with one).</p><p>Yes dictation of texts is useful and yes she reduces the amount of time spent fiddling with dials and switches but shouldn’t we be able to ask “show me what the traffic is like on the M1 ahead” when attempting to avoid those pesky Sunday drivers?</p><h4>Apple Mac</h4><p>Mac has really felt unloved in recent years. The new Macbook was released and drew plaudits. It also still has one USB port…for now! But I’ve never understood why Siri hasn’t been on the Mac until this point.</p><p>Multi-tasking (for males especially) is a daunting task but I have often found myself in the middle of a long email or constructing a detailed document and wishing to find a quick way to multi-task. I have to exit the app/window I am using, open the new one and then snap it next to the other so they run side by side.</p><p><strong>Wouldn’t it be far more scrumptious to just call on Siri to do that for us?</strong> We ask her to search the web for the URL or content in Finder we’re after and in a similar manner to which the Notification Centre appears on the right side, her results animate in without a touch of a button &amp; more importantly without even having interrupted my workflow/typing.</p><blockquote>I’m a firm believer that <strong>sooner or later, voice will be THE choice!</strong></blockquote><h4><strong>The possibilities would be quite simply endless for developers.</strong></h4><p>A lot of what I have written above is based upon speculation on my part but it’s an interesting time to think about the direction this could have on the Apple ecoSystem.</p><p>I genuinely believe that this shall be the <strong>biggest WWDC we have ever had</strong>, since iPhone. I believe that because Siri &amp; voice have the opportunity to completely elevate the entire suite of products that Apple offers. Siri has not been upgraded for 4 years really and I find it very troubling and difficult to believe that Apple has done little to innovate over that time, despite planning their redonkulous new offices.</p><h3>The Questions That Need Answering…</h3><p>A difficult decision that Apple has (perhaps had) to make is <strong>how Siri interacts with these third party apps</strong>. I highlighted this above but do users need to call and name the specific app in the command that they wish to interact with? Does Siri present several options back before the content?</p><p>There’s also questions like <strong>how do developers ‘program’ Siri</strong> with these commands, will we see a separate voice platform accompanying Xcode or will this become part of iTunes Connect?</p><p>Also <strong>which devices does Apple offer support to in the Siri SDK</strong>. Recently they’ve rolled out software upgrades exclusively across new products, but this could have such an immense impact on their brand that they may be foolish to restrict it to just those newbies.</p><h4>Despite all the uncertainty, it’s going to be incredibly exciting what Apple have in store for us in the coming weeks. Just so long as they don’t announce anymore 16GB iPhones…</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f611ae563ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our New ‘Smashing’ Tennis Website is Live]]></title>
            <link>https://medium.com/@david_west/our-new-smashing-tennis-website-is-live-a203967f204a?source=rss-94d4ef5c2af7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a203967f204a</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[tennis]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[David West]]></dc:creator>
            <pubDate>Tue, 19 Apr 2016 01:42:39 GMT</pubDate>
            <atom:updated>2016-04-19T01:42:39.240Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1lo3ZRcX_hpHIYyQMkVI-A.png" /><figcaption>ScoreLord — Tennis iOS App — Website Live!!!</figcaption></figure><p><strong>Tennis?</strong> I hear you ask. <strong>iOS</strong>? That’s surely been done before. Well, not like this it hasn’t. *Activate sales mode*</p><p>Whilst ramping up development of our new iOS tennis app (did we mention it’s for tennis lovers / players / watchers on iOS?), we have finally got around to modifying our website so that we can showcase what we are trying to achieve in the world of tennis &amp; tech.</p><p>Do sneak a peek over at <a href="http://www.scorelord.co/"><strong>www.scorelord.co</strong></a> &amp; leave a comment below to tell us how awful you think it is. Seriously though, do be constructive and let us know how we can improve on the existing style &amp; do advise if our message, our app’s offering or anything else could be made any clearer. Do also take the opportunity to tell us what you do like, if you’re a “glass-half-full” kind of kid, like this little Djoker:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*UaZSI5kwe4X7SqH4wHhQHw.jpeg" /><figcaption>No Djoke, I‘m still being bottle fed…</figcaption></figure><p>If you are interested in our project and love playing the game of tennis, we would of course <strong>love it if you decide to leave an email behind on our page </strong>so we can keep you informed of developments. Who knows, maybe we’ll even invite you to beta test the product, weeks in advance of anyone else. Totally worth it, right?</p><p>We’ll also definitively be offering special early subscribers a nice rosy discount on our premium subscription as soon as the app is released. That is of course dependent upon you providing us with one of your ‘spam’ account addresses. We won’t spam you though, trust. It’s just we know…your email address is precious…we get that!</p><p>That said, if you want to say hi, you can contact me directly via <a href="/service/mailto:david@scorelord.co"><strong>david@scorelord.co</strong></a><strong>. </strong>I’ll be sure to respond to each and every person/bot/troll that makes their way into my inbox. Promise.</p><p>On to more serious note though, what can you expect from this page in the coming weeks? Well we’ve pulled together a list of future posts &amp; topics we will be looking to cover off:</p><ol><li>Full Feature &amp; Functionality List</li><li>Apple Watch — Your Real Tennis Partner</li><li>Apple iPhone — How To Score Matches In-Game</li><li>Building on iOS — Hiring Developers &amp; Tips</li><li>User Testing on iOS — Lessons Learnt</li><li>Releasing on iOS — Release Results</li><li>User Reviews — Beauty &amp; The Beast</li><li>Version 2 — Feature List &amp; PUBLIC VOTE!</li></ol><p>Let us know also if you want us to add anything else to that list. We have big ears. Hopefully we’ll hear your feedback soon. Over &amp; out…</p><p>David @ ScoreLord.co</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a203967f204a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Swift: Doing the PanPan in…UICollectionView]]></title>
            <link>https://medium.com/@david_west/becoming-a-fan-of-uipan-gesturerecognizer-a4d48e5cfb17?source=rss-94d4ef5c2af7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4d48e5cfb17</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[David West]]></dc:creator>
            <pubDate>Tue, 05 Apr 2016 23:47:15 GMT</pubDate>
            <atom:updated>2016-04-19T16:18:10.521Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*ZMo8O1s8CZTV2O3OOULeuA.jpeg" /><figcaption>These two have fallen deeply in love!</figcaption></figure><p>Despite it’s own panning capabilities, UICollectionView can double-pan, so let’s see how…</p><p>But first, in spite of <a href="https://medium.com/@davidrwest/forget-resolutions-focus-on-solutions-learning-swift-code-952b2b87c836">my previous intentions</a> to post a lot of Swift Solutions on this platform, I’ve been pretty lacklustre at sharing my new found experience of Swift in recent months. I admit. However I will be sharing a lot more in due course, including on my upcoming app release, so do go ahead &amp; follow.</p><figure><a href="http://scorelord.co/wp-content/uploads/2016/04/findopponentgif.gif"><img alt="" src="https://cdn-images-1.medium.com/max/206/1*d_Bwyvuuk-pG9my_8n-kbw.gif" /></a></figure><blockquote>I am currently in the midst of building a <strong>social tennis scoring app within iOS</strong> and up until this week, have gone about doing so alone. As the summer season approaches, people are dusting off their rackets and their smelly fuzzy balls. There is now an added impetus to get the app shipped in time for inevitable tennis fever. This week I’m therefore <strong>scouting for experienced iOS developers</strong> to help get the job done over the coming weeks. Therefore if you like the look of what I’m trying to achieve here and want to join the team, do please get in contact via <a href="https://twitter.com/davidrawest">https://twitter.com/davidrawest</a> or <a href="https://medium.com/u/94d4ef5c2af7">David West</a>.</blockquote><p>In the meantime…it’s time to show you what wonderful things you can achieve with CollectionViews…</p><h4>1. SET UP UICOLLECTIONVIEW</h4><p>First (assuming we have added the UICollectionView within Storyboard and set-up a custom UICollectionViewCell)…we need to add the following commands:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b5f70862f15a34d6ac4db2dff7c3bc15/href">https://medium.com/media/b5f70862f15a34d6ac4db2dff7c3bc15/href</a></iframe><h4>2. SET UP VARIABLES</h4><p>Next we need to ensure that the IBOutlets and Variables we will later refer to once a Pan is initiated, are present within our custom class for the UIViewController…</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/90847ccb6b1b71d8c440bbacd7bd4892/href">https://medium.com/media/90847ccb6b1b71d8c440bbacd7bd4892/href</a></iframe><h4>3. SET UP A CUSTOM SCROLLVEIWDELEGATE FOR UICOLLECTIONVIEW</h4><p>Thanks to <a href="https://medium.com/u/f6ab9b8a2232">DucTran.io</a>, I came across this custom scrollView delegate for UICollectionView, which allows for cycling horizontally through each cell, like pages. You could add in some bounce animation here, but each cell will settle in place when it comes into view. Make sure to <a href="https://www.youtube.com/watch?v=_d-xZv0JrRE">check out his tutorial on UICollectionViews</a> here for some further setup information. He’s a boss!</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bf022acc23db84d0ad2c5b30fdd3609a/href">https://medium.com/media/bf022acc23db84d0ad2c5b30fdd3609a/href</a></iframe><h4>4. THE FUN STUFF — IMPLEMENTING PANGESTURES</h4><p>So let’s start implementing the PanPan. First within ViewDidLoad, we want to initiate the PanGestureRecognizer and assign it to the UICollectionViewCell…</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2bc8126faa3fd14e8a224d6f822d2a15/href">https://medium.com/media/2bc8126faa3fd14e8a224d6f822d2a15/href</a></iframe><p>We then want to add this next little snippet below the CollectionView functions we added within Section 1.</p><p>This is SOOO imperative as it basically only applies the PanGestureRecognizer to the UICollectionView if we are <strong>swiping up or down</strong>. It won’t recognise or apply the panGesture if the swipe involves more horizontal than vertical ‘panning’ and this is necessary because we have our UICollectionView scrolling left to right to display different UICollectionViewCells. We don’t want to interfere with that:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/49e6821c457248969ef51f0138cfab0b/href">https://medium.com/media/49e6821c457248969ef51f0138cfab0b/href</a></iframe><p>Woop…almost there…</p><h4>5. FINAL STEP — LETS DETERMINE WHAT HAPPENS WHEN WE PANPAN</h4><p>Ok, I lied a little…this is a lengthy last step but it is the last! But don’t worry…we’re almost done!</p><p>Here when the panGesture begins, we are <strong>creating a UIImage of the CollectionViewCell </strong>and casting it to a new UIImageView (called movingCell). This is because CollectionViewCells are notoriously difficult to move around and it is just far easier this way creating a copied image than overriding Apple’s syntax. Plus, you can reduce the transparency on the cell for a nice effect to show where it was ‘previously’ positioned.</p><p>We are then setting the frame of that new imageView to the same as the CollectionView cell and restricting the movement by fixing the x axis to originalCenter.x. We don’t want for our cells to move left and right like Tinder, just up and down. The center.y axis will change according to the location of the panGesture in the CollectionView (defined at the top of the function).</p><p>We are also setting a UIView (which I have not previously mentioned until now of bgBlur to an alpha of 0.15. This is simply a <strong>UIView with black background floating on top of the UICollectionView</strong> (but importantly…below the movingCell image we have created). It makes for a nice but simple effect, to add depth to the screen.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/48ab75bbd83c4e68c5fe0bf77879ddba/href">https://medium.com/media/48ab75bbd83c4e68c5fe0bf77879ddba/href</a></iframe><p>The last half of this code (below “add arrow on top of..”) is to <strong>present an arrow </strong>when the pan begins, similar to the new Instagram feature you see in the picture. I also added a label below the new image, prompting users to keep scrolling up to view the UIActionSheet:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KHdIAeLV0gEoT7Ugi8BAKQ.jpeg" /><figcaption>Image Courtesy of iMore — <a href="http://www.imore.com/best-apps-3d-touch-iphones-6s">http://www.imore.com/best-apps-3d-touch-iphones-6s</a></figcaption></figure><p>Now normally you would add a load of code into the .Changed state of the UIGestureRecognizer but I needed not in this case. Here, we assign the <strong>center of both the arrow and the label</strong>; to the top &amp; bottom respectively of the ‘fake’ collectionviewcell, created above.</p><p>We are also <strong>animating that cell if it passes a certain threshold</strong> (and goes above 80 pixels from the center of the screen). If so, it animates up to the top of the screen with a little spring and brings up the action sheet (which we will customise shortly). This is the code that follows the UIGestureRecognizerState.Began status we defined just above:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/181906a64cb6daecabdc5d5b58b65e8e/href">https://medium.com/media/181906a64cb6daecabdc5d5b58b65e8e/href</a></iframe><p>Then we need to deal with what happens when the pan ends. Here we just need to handle what happens when we don’t exceed the threshold of 80 pixels from the center of the screen. We also then animate the image to <strong>a) snap back to the middle, b) fade out &amp; c) be removed from view</strong>. We also change the alpha and transparency of the cell once more to 1.0, and the blur to 0, so the actual collectionViewCell is shown in all its glory once more.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3e12c67d97acebc9028d50cecbabfdd7/href">https://medium.com/media/3e12c67d97acebc9028d50cecbabfdd7/href</a></iframe><p>And so that’s pretty much it… although if you were paying close attention, you’ll remember that we wanted to call a customised version of the action sheet to handle some extra options, including:</p><ol><li><strong>Challenge Opponent</strong> (which will present a modal in the future to start a tennis match)</li><li><strong>Add the Opponent to our contacts</strong> (right now it just displays the contacts icon at the bottom of the screen for a few seconds).</li><li><strong>Delete the Opponent</strong> from our search results (shooting the card up and out of the screen… and will in future remove the data from the Array of Opponents, animating the next CollectionViewCell into view).</li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a3a5715a2cf8c9d039f5ab8416344dcb/href">https://medium.com/media/a3a5715a2cf8c9d039f5ab8416344dcb/href</a></iframe><p>Gosh, sorry for you mobile readers… that was quite a block of code that last bit. However….now we have this lovely UI and we have successfully implemented panGestureRecognizer on UICollectionViews, which is often a troublesome task.</p><p>I hope you’ve followed this properly and without too much fuss. If not, feel free to ask me any questions about this if you’re puzzled… and do let me know how you get on with your own projects implementing this. I’d love to see an example in a vertical CollectionView with horizontal panning!!!</p><p>Here’s the GIF once more:</p><figure><a href="http://scorelord.co/wp-content/uploads/2016/04/findopponentgif.gif"><img alt="" src="https://cdn-images-1.medium.com/max/206/1*d_Bwyvuuk-pG9my_8n-kbw.gif" /></a></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*XfJTdI7RLhtR3QkZMeh3Zw.png" /></figure><h4>Over and Out…</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4d48e5cfb17" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Forget New Years Resolutions – Just Be Swift @ Swift]]></title>
            <link>https://medium.com/@david_west/forget-resolutions-focus-on-solutions-learning-swift-code-952b2b87c836?source=rss-94d4ef5c2af7------2</link>
            <guid isPermaLink="false">https://medium.com/p/952b2b87c836</guid>
            <category><![CDATA[new-years-resolutions]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[David West]]></dc:creator>
            <pubDate>Thu, 31 Dec 2015 17:07:33 GMT</pubDate>
            <atom:updated>2016-04-06T00:20:20.510Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Pjy0YDtBdJmQLaKFrMnPQ.png" /><figcaption>Solutions &gt; Resolutions</figcaption></figure><p>So it’s that exact time of the year when people share their goals with one another for the upcoming year, knowing full well that they will be metaphorically waving a white flag/hankerchief/tea-towell/tissue (wave as appropriate) soon enough in their pursuit of self-improvement for the year of 2016.</p><p>2015 was a year like that for me. 2015 was a year of sacrifice. 2015 involved moving cities, countries &amp; climate to improve as a person. 2015 involved postponing a 7 year career. 2015 involved no office job no more. In 2015 I focused on learning a new language. In 2015 I dabbled with Xcode. In 2015 I bossed Photoshop. In 2015 I still came up short!</p><p>Despite the sacrifices, despite the empty days, despite living the life all of us have craved… I still achieved little more than I would have if 2015 had been 2014, without the sacrifices. The problem was that <strong>those resolutions were not very resolute</strong> at all. 2016 cannot be another year of chasing rainbows. <strong>2016 is not one for resolutions…</strong></p><h3><strong>Self-Discipline</strong></h3><p>I (vaguely) remember writing my final year dissertation at University on “Implementation Intentions” and how their implementation intend to implement habits. And yes I intended to make that sound <em>that</em> interesting… it was a thrilling read (where’s the sarcasm font?).</p><p>The problem I have since encountered is that with these “IIs” or “SMARTER Targets” (as the business world will have you regurgitating) is that they require self-discipline &amp; assume that life in any given year is linear, simple &amp; without distraction.</p><p>Of course we need our objectives…but if you’re anything like me; you will find distractions from the unlikeliest of sources. Even for an activity like skiing… glistening with enjoyment… there will be times when procrastination, doubt &amp; distractions will surface to throw you off the productivity piste &amp; push you deep into that all too comfortable &amp; familiar yellow snow. Painfully &amp; smellily.</p><blockquote>Smellily: A word made-up (that does not exist in the english language) to convey a metaphor to Medium readers of being in the midst of a very stinky situation.</blockquote><p>I’m sure there’ll be no shortage of posts in the coming 48 hours advising how to get back up from such a scenario, to fight through the pain barrier &amp; climb that mountain once more. This is not one of those posts.</p><p><strong>2016 for me is going to be a year focused on solutions.</strong> In the pursuit of knowledge in Swift &amp; iOS Programming this year, I will be focusing on ticking-off &amp; adding-to an extensive list of functionality, in order to progress <em>swiftly</em> in the world of iOS development. Without such a guideline, learning to code in Swift is simply going to be as unobtainable as it was the year prior.</p><h3>Resolutions &gt; Solutions</h3><p>The below list of functionality for Swift &amp; iOS Projects is what I have deemed to be important learning so far. It’s a wish list, having dabbled in Xcode towards the end of last year. This list will be updated &amp; added-to throughout 2016 (depending on progress). I’ll also attempt to write-up supporting pieces on this platform &amp; providing links to each solution, to share my findings &amp; all my learnings along the way. I will be doing this whilst co-developing a new sports scoring app ready for the middle of the year. So here’s the hit-list (be sure to let me know if I have missed anything?):</p><p><strong>NAVIGATION</strong></p><ol><li>Linking Storyboard ViewControllers to other Storyboard VCs</li><li>Custom Back button using code &amp; without UINavigationBar</li><li>Embedding Views &amp; XIBs within different ViewControllers (container views, scroll-views, table-views) without Storyboard</li><li>Collapsable Animated Bottom Tab-Bar Menu</li><li>Create alternative, interactive Menu other than the greasy, over-used Hamburger menu.</li><li>Implement intuitive app walkthroughs (without sliding through 3–5 pictures) upon first use of functionality</li></ol><p><strong>LOGIN</strong></p><ol><li>Firebase login for users using Facebook, Twitter, Email</li><li>Incorporating TouchID Authentication to remove need for text input</li><li>User access to aspects of App without Signing-Up/In</li></ol><p><strong>ANIMATION</strong></p><ol><li>Bounce &amp; Elastic animations without external frameworks/pods</li><li>Subtle shake animations for drawing attention to calls-to-action</li><li>Implementing pull-down to refresh animation</li><li>Implementing custom alert / modal views for info</li><li><a href="https://medium.com/@davidrwest/becoming-a-fan-of-uipan-gesturerecognizer-a4d48e5cfb17#.p9vd3y6h9">Working with UIPanGestureRecognizer</a> — DONE!</li></ol><p><strong>MAPS</strong></p><ol><li>View GoogleMaps or AppleMaps Data within a View</li><li>Use GetLocation to populate address fields &amp; mapView</li><li>Display directions to a Map location &amp; punch-out to native app</li></ol><p><strong>SOCIAL</strong></p><ol><li>Importing/Inviting friends from Facebook &amp; Twitter (perhaps more)</li><li>Sharing data, maps &amp; images to friends on Facebook &amp; Twitter</li><li>Automatic posting &amp; sharing to Facebook &amp; Twitter</li><li>Implementing Facebook Events to target/advertise to specific users</li></ol><p><strong>DATA &amp; LOADING</strong></p><ol><li>Linking user &amp; community data to Firebase back-end</li><li>Storing data for user(s) until approval to make public</li><li>Using CoreData &amp; Caching Data</li><li>Implementing MultiPeerConnectivity via Bluetooth</li><li>Performing Background Fetch for Up-To-Date Information</li></ol><p><strong>VOICE RECOGNITION</strong></p><ol><li>Voice recognition to prompt certain actions within app</li><li>Voice recognition to prompt actions outside of App (possible?)</li><li>Voice output from Siri based upon actions/scores</li></ol><p><strong>APPLE WATCH</strong></p><ol><li>Create Apple Watch App from nothing but Glances</li><li>Implement Haptic Alerts when using App</li><li>Implement Voice Recognition (see above)</li></ol><p><strong>SETTINGS</strong></p><ol><li>Implement tens of different colour schemes and allow user-choice</li><li>Add premium IAP/subscription for extra un-lockable functionality</li><li>Multiple Languages &amp; automatic selection based on Location/iCloud</li></ol><p><strong>EXTRAS</strong></p><ol><li>General Push notifications after certain usage (no. of time/actions)</li><li>User specific Push notifications when activity concerns them</li><li>Push notifications that allow custom actions (background/foreground)</li><li>Implementing force-touch &amp; 3D touch for more than navigation</li><li>Sound effects within app, that do not disrupt/end music</li><li>Implement beautiful graphs (with animation) using ios-charts</li></ol><p>For those wishing to help me tick-off this list of items quickly, I encourage you to share your StackOverFlow, RayWendy &amp; YouTube links to help me find the best learning resources out there &amp; help us newbies all achieve more this year. I would also appreciate any recommendations for additions to the list, to help me become a more rounded developing dev.</p><p>I plan to do a 30 iOS apps in 30 days challenge at some point in the near future, probably around the second quarter so I will keep you informed of my progress on that nearer the time.</p><p>However <strong>2016 is the year of just getting it done.</strong> No more false promises, no more delays, no more sacrifices, no more resolutions. Just swift.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*u0sLyEKSvuW3PN0R7DH1oQ.gif" /></figure><h4><strong>2016 is about Solutions Not Resolutions.</strong></h4><h3>So tell me, what are you not going to achieve again this year?</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=952b2b87c836" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>