56: Special Opportunity episode artwork

EPISODE · May 3, 2015 · 53 MIN

56: Special Opportunity

from Mobile Couch · host Mobile Couch

Jake has his watch in hand, so after going back over some unit testing follow-up, and with a single weekend’s experience, the couch looks at first impressions, the various delays that people are struggling with, and handling multiple asynchronous tasks with dispatch groups. Jelly segues seamlessly into follow-up, and talks about how he spent some time since the previous episode creating unit tests for one of his open source projects. He struggled a little with getting started, but feels like the endeavour was worthwhile (it found bugs!). He’s still wary about full test-driven development though. Pre-ordered watches have started arriving, including Jake’s, and so the couch discusses the pre-order experience, Apple’s offer of expedited orders to random developers, and the watch labs that were offered prior to the launch for on-device testing of Apps prior to day one release. This leads to both Jake and Jelly giving their first impressions, including the delay that they experienced with waiting for Jake’s glance to load it’s data, and the fact that there’s a large gap between the experience of first-party and third-party apps. Jelly uses this as an opportunity to cover what gives him the inspiration for his apps, and how being the first in the store doesn’t prevent someone from coming along with a better implementation and succeeding. Moving along, Jake talks about an issue he had this week with implementing multiple API calls for displaying data in a today extension. After trying a few solutions (including NSOperationQueue), and then he discovered dispatch groups, so after he covers how he implemented them, the couch discuss why you would choose them over an operation queue. This spawns a conversation about APIs and how Jake’s implementation is covering up a potential issue with the API he’s using. Is it better to use a potential complex API endpoint that doesn’t provide the data in the format you need, or stick a server between the app and the API to parse out just the bits you need? Also, did you know Jake got an Apple Watch?

Episode metadata supplied by the publisher feed · Published May 3, 2015

Jake has his watch in hand, so after going back over some unit testing follow-up, and with a single weekend’s experience, the couch looks at first impressions, the various delays that people are struggling with, and handling multiple asynchronous tasks with dispatch groups. Jelly segues seamlessly into follow-up, and talks about how he spent some time since the previous episode creating unit tests for one of his open source projects. He struggled a little with getting started, but feels like the endeavour was worthwhile (it found bugs!). He’s still wary about full test-driven development though. Pre-ordered watches have started arriving, including Jake’s, and so the couch discusses the pre-order experience, Apple’s offer of expedited orders to random developers, and the watch labs that were offered prior to the launch for on-device testing of Apps prior to day one release. This leads to both Jake and Jelly giving their first impressions, including the delay that they experienced with waiting for Jake’s glance to load it’s data, and the fact that there’s a large gap between the experience of first-party and third-party apps. Jelly uses this as an opportunity to cover what gives him the inspiration for his apps, and how being the first in the store doesn’t prevent someone from coming along with a better implementation and succeeding. Moving along, Jake talks about an issue he had this week with implementing multiple API calls for displaying data in a today extension. After trying a few solutions (including NSOperationQueue), and then he discovered dispatch groups, so after he covers how he implemented them, the couch discuss why you would choose them over an operation queue. This spawns a conversation about APIs and how Jake’s implementation is covering up a potential issue with the API he’s using. Is it better to use a potential complex API endpoint that doesn’t provide the data in the format you need, or stick a server between the app and the API to parse out just the bits you need? Also, did you know Jake got an Apple Watch?

PodParley-generated summary based on available episode metadata and transcript content.

NOW PLAYING

56: Special Opportunity

0:00 53:30

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

Mobile Money by moomoo Mobile Money by moomoo Hear from seasoned traders, financial influencers, and industry insiders as they discuss money matters and market news and share their personal finance stories.Disclaimers: https://www.moomoo.com/us/support/topic4_523 MySwimPro Swimming Technique & Training Podcast MySwimPro MySwimPro is the number one fitness application for the fastest growing sport in the world. Since 2014, we have been on a mission to help swimmers of all levels live happier and healthier lives through swimming. Today, swimmers in more than 150 countries use MySwimPro’s award-winning mobile and wearable apps to access personalized swim workout plans, training plans, educational drills and videos, advanced analytics, and to log and track their progress. MySwimPro is accessible on iOS and Android smartphones and wearables, and is free to get started. Mobile App Development TV (Video – 480p) MobileCast Media, Inc. Tune in regularly for the latest tips and best practices for successfully managing mobile app development projects. GetConnected Curiouscast How is technology changing our lives? Hosting interviews with innovators, execs, and more, Canada’s tech expert Mike Agerbo explores how everything from tech gadgets to internet culture are changing our world.For over 20 years, Mike Agerbo has made technology simple for audiences. He brings the latest gadgets to Global TV audiences with his weekly Noon Hour News Tech Talk segment and hosts the popular tech TV and YouTube show GetConnected. He also hosts The App Show, a radio show all about mobile technology. 

Frequently Asked Questions

How long is this episode of Mobile Couch?

This episode is 53 minutes long.

When was this Mobile Couch episode published?

This episode was published on May 3, 2015.

What is this episode about?

Jake has his watch in hand, so after going back over some unit testing follow-up, and with a single weekend’s experience, the couch looks at first impressions, the various delays that people are struggling with, and handling multiple asynchronous...

Can I download this Mobile Couch episode?

Yes, you can download this episode by clicking the download button on the episode player, or subscribe to the podcast in your preferred podcast app for automatic downloads.
URL copied to clipboard!