Software developers write code for a living, but there is more that goes into shipping software than writing its code. And while diving deep into programming language or framework is a great way to improve one's craft, there are other, often more effective, ways to improve that do not require writing code. This talks shares a set of techniques for leveling up as a software developer across three areas: The work. The not-work. The team-work. For each area, three techniques are provided. The aim of the talk is to broaden the audience's perspective on what it takes to "be productive", and to arm them with new tools to deploy at work. The talk doesn't want to be prescriptive, but rather informative and inspiring.

Gio is a mobile infrastructure engineer working remotely with Automattic, the makers of WordPress.com, Tumblr, Pocket Casts, and more. He writes about software and productivity at https://giolodi.com and recently published Test-Driven Development in Swift with Apress. When he's not working or spending time with his kids, you'll likely find him reading or practicing to reach "sub-30" on the 3x3 Rubik's cube.

In your app development, are you on a journey of migrating your networking API to GraphQL? While we are all excited about not being restricted by the API endpoints any more, and having only one schema to be shared among all the frontend platforms, and even the offline experience that GraphQL can provide with the local caching, do you also face some of these challenges? - While the GraphQL schema seems to work well on web platform, it does not work with your mobile experience. - You are having no idea what the schema provides. The GraphQL data is difficult to understand. - When consuming data, each platform requires additional logic. - Breaking change happens very often and sometimes ends up with production issues. - Older version apps are always a problem when the GraphQL schema change is deployed. - Consuming the schema out of the codeGen ended up with a lot of unnecessary guards in the code base and wired syntax in swift. This talk will cover the best practises for designing GraphQL schema for the app experience. We'll work out the schema design together for a real-life app experience, with some bad designs, and see where the problems are, from structure to fields. By the end of it, hopefully you'll be able to know the principles and practises of schema design and be able to influence how your graphQL schema contract should look like in order to make the best of your app experience, including the older version apps.

Amy is senior iOS developer working at SEEK, passionate about solving problems with clean code, and an advocator for best practises and fostering a clean code culture. In the past few years, Amy has migrated a number of networking APIs to GraphQL in the SEEK iOS app. Last year, Amy led a mobile app development team that migrated a six-year-old legacy component to GraphQL across Android, iOS and Web platforms.

We've seen a lot of our friends and colleagues move to the US in the past few years and for a lot of people, it's their dream (it was mine, at least) to make the jump work at one of the big tech companies. This talk will cover what it's like to work at a large tech company and how it can be so different from the usual Apple dev role in Australia/NZ. My talk will cover the pros, cons and differences of working at these companies and give the audience a good insight on what to expect if they ever decide to make the big move across the Pacific Ocean. It will also cover a lot of the benefits of working in Australia in comparison and I'll discuss some of my reasons for moving back.

My name is Andyy Hope, you may know me from my Apple dev conference in 2017, Playgrounds Conference. Since Playgrounds, I've had the opportunity to experience working at a couple of the familiar big tech companies, Meta (previously known as Facebook) and Twitter.

The *accessibility gap* is the gap between having a passing familiarity with the accessibility APIs, and being able to wield them effectively to create great accessible experiences. Accessibility has been a focus for Reveal for the last few years, and our work has been motivated by wanting to help developers and mobile teams close this gap. Most accessibility advice online starts from the bottom, assuming no prior knowledge, and will often include lengthy justifications for *why* you should make your app accessible. We’re going to assume you already recognise and respect why it’s important that your app is accessible to as many users as possible. Using Reveal's Accessibility and Insights workspaces, we'll go through a real-world app and show how choices affect the accessible user interfaces differently, and how to create a better experience, using concrete, actionable examples. The goal is for you to leave this talk with approaches and tools that you can apply to your own apps.

Chris Kolbu is a senior iOS/macOS developer at Itty Bitty Apps. He cares deeply about accessibility, user and developer experience, software testing, and performance. He does not care for Christmas being in summer, but is getting used to it. Tony Arnold has been developing for Apple’s platforms for over 20 years, and leads the delivery of Reveal at Itty Bitty Apps. Tony and Chris are the current developer team behind Reveal, a development tool used to debug and improve apps on Apple’s mobile platforms for almost a decade.

With SwiftUI clearly here to stay and in awe of its power, capabilities and simplicity, Tristan W. Reed and David A. McMeekin decided to adapt the content of their existing “Introduction to iOS Development" MOOC to SwiftUI (where possible) when adapting the MOOC as an internal undergraduate unit at Curtin University. Tristan will speak about some of the issues encountered in adapting the course for SwiftUI, considering different devices, alongside some of the benefits from both the perspective of the educators and from the perspective of the students themselves - including benefits with using non-Apple frameworks!

Tristan W. Reed is an academic at Curtin University, a software engineer who enjoys utilisting and teaching Apple tools and frameworks to others as well as use software technologies to solve problems in the real world.

In recent years, machine learning has become crucial in shaping how we interact with devices and services. However, building machine learning applications that prioritize the needs and privacy of users can be a complex and challenging task. This talk will explore how to use Core ML and Create ML to develop user-centred machine learning experiences using Apple platforms. We will focus on the advantages of using on-device machine learning, including speed and privacy benefits over cloud-based approaches. We will also discuss making machine learning accessible and inclusive for all users, regardless of technical background. Additionally, we will delve into privacy in machine learning and how to design applications that respect user data and maintain trust. Join us to discover how to build thoughtful and user-centred machine-learning experiences for Apple platforms.

James Dale is an entrepreneur and developer specialising in iOS App Development. Currently, he is leading App Development studio, Friday Technologies. Previously, he cofounded US-based startup HAGS, backed by Google and BoxGroup (now acquired by Snapchat). James is the recipient of four Apple WWDC Scholarship awards, and a serial iOS app developer creating apps such as CleanSky and RulAR. He previously worked at Apple in the ISE Special Projects and Machine Learning Platform & Technology teams, contributing to the Create ML framework and macOS app. James speaks often at iOS and Swift industry conferences, and teaches online Swift courses with RMIT University. James is driven to create change in the mobile apps and machine learning spaces! Keep up to date with James on Twitter at @_JamesDale.