• Day 75 of #100DaysOfSwiftUI: can we fix it?

    Overheard today, in a setting particularly lacking in any form of jet propulsion: “It really is rocket science.”

    Nope. Just like implementing accessibility in your SwiftUI apps. Objectively not rocket science. 🚀 🤔

  • Day 74 of #100DaysOfSwiftUI: open arms

    Delighted to see @twostraws include accessibility information in the core of this course.

    Apple generally do a great job of providing an accessible platform, and the least developers can do is make sure their software is inclusive!

  • Day 73 of #100DaysOfSwiftUI: always cutting corners

    Breaking: I didn’t complete this by the time WWDC started!

    “I love deadlines. I love the whooshing noise they make as they go by.” — Douglas Adams

  • Day 72 of #100DaysOfSwiftUI: authentication

    With biometric sensors commonplace in technology now, why are they not used more routinely to log in to devices and access data and services? In addition to passphrases, if trusting the tech is the problem.

  • Day 71 of #100DaysOfSwiftUI: standing on the shoulders of giants

    Given how easy it is to access and repackage so much of the world’s data, in many cases without cost either developer or consumer, is it any wonder the percieved value of software has mostly diminished over time?

  • Day 70 of #100DaysOfSwiftUI: make mine a triple

    Is completing more than one ‘day’ per day outwith the spirit?

  • Day 69 of #100DaysOfSwiftUI: matching touch

    With only a “month” left to go until completion, I should really start thinking about a project to put this new found knoweldge to good use. Suggestions welcomed.

  • Day 68 of #100DaysOfSwiftUI: extensions

    There have been a few points in the SwiftUI course where there have been small extension exercises and challenges - they are really good at making you think about what has just been covered. More of this please.

  • Day 67 of #100DaysOfSwiftUI: mastery

    I got wrong answers in the review quiz! Too much beer? Careless reading of questions? Formative assessment is only truly useful if you make mistakes? Or should I hang my head in shame?

    My latent teenage brain suggests the latter.

  • Day 66 of #100DaysOfSwiftUI: avoiding the evil horrors

    Beer coding. I guess it’s okay, since this is not my day job, right? Be fascinating to see how much I rememember tomorrow.

  • Day 65 of #100DaysOfSwiftUI: instacode

    Continued adventures in UIKit. Finished just in time to watch a SpaceX launch - and then it was canceled. 🚀 🚫

  • Day 64 of #100DaysOfSwiftUI: just say no

    It’s almost as if Paul Hudson (@twostraws) designed his SwiftUI course as he did in order to turn new developers away from UIKit. I used to quite like the delegate pattern - maybe I still do.

  • Day 63 of #100DaysOfSwiftUI: four image types of the apocalype

    CIImage ➡️ CGImage ➡️ UIImage ➡️ Image

    “at least it’s not snowing, pokety poke poke poke” — Drew Carey

  • Day 62 of #100DaysOfSwiftUI: result is binding

    I am now officially behind schedule for finishing this course before WWDC. So, either I live with that, or I double down on some of these information days and push for 22 June…

  • Day 61 of #100DaysOfSwiftUI: crashes of indeterminate origin

    A restructuring of the struct version of FriendFace to support CoreData, but with lingering issues of poor thread management. Insomnia or not, it’s late to be fixing anything.

  • Day 60 of #100DaysOfSwiftUI: bread and butter

    Enough developers must need to circumvent the navigation stack hierarchy that SwiftUI would benefit from a baked in a dismissToRootView() (or similar) method.

  • Day 59 of #100DaysOfSwiftUI: always sorting

    Long weeks beget short comments.

  • Day 58 of #100DaysOfSwiftUI: new relationships

    So, the big take away from the last couple of days is that the next SwiftUI update would really benefit from better CoreData integration - I have a soft spot for Objective C, but I don’t need the hipster nostalgia.

  • Day 57 of #100DaysOfSwiftUI: wax on, wax off

    Not all of the 100 days can be building cool little apps, sometimes the learner must work through the basics.

    Bonus excitement of the day? Publishing this directly from IA Writer - but I would prefer the title field to be optional.

  • Day 56 of #100DaysOfSwiftUI: always reading

    As an aside, related to the topic of the now completed Bookworm project, if you would like a book recommendation, why not try the KESTREL series by Edinburgh-based author, Matt Gemmell.

    Enjoy. 📚

  • Day 55 of #100DaysOfSwiftUI: self-flagellation

    Completed a book tracking app today. Entered some test data of books I have read to check that everything works as intended. Judging my own taste as each book springs to mind Just me?

  • Day 54 of #100DaysOfSwiftUI: underrated emoji ratings

    SwiftUI as a design abstraction can occasionally feel unnatural. I hope rough edges are smoothed out rather than relying on developer experience to cope.

    But the power of view composition/decomposition is considerable. 💯

  • Day 53 of #100DaysOfSwiftUI: supersize me

    The Xcode SwiftUI canvas incorrectly reports the size class of phones as .regular (rather than .compact). The simulator behaves as expected. Perhaps Xcode is returning my MBP’s size class? Perhaps not. The suspense.

  • Day 52 of #100DaysOfSwiftUI: always dealing

    Another project complete, including challenges. Not much more to say.

  • Day 51 of #100DaysOfSwiftUI: aka groom lake

    Today I learned about REQ | RES. A great tool which simulates a web API endpoint for testing your client code. Very neat. Very simple.