Gone Mobile

In this episode of Gone Mobile, Jon and Allan discuss a variety of topics ranging from sports team loyalty to the intricacies of app development. They delve into listener feedback about coding with AI tools like ChatGPT and Copilot, share insights on navigating iOS and Xcode updates, and explore new features in the iPhone 16. The conversation also covers updates in Maui and .NET, the importance of staying current with technology, and Jon's personal project of creating a snack app for Disney World. They conclude with a discussion on building a content button in Maui and the challenges of cross-platform development. Takeaways Listener feedback is crucial for app development. AI tools can enhance coding but require understanding. Staying updated with iOS and Xcode is essential for developers. Maui and .NET updates bring new features and improvements. Creating a snack app can be a fun personal project. Cross-platform button development presents unique challenges. Documentation is key for using libraries effectively. Unit testing is important for ensuring code quality. Engaging with listeners can lead to interesting discussions. Future content may include coding demonstrations. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Sports and Team Loyalty 02:57 Listener Feedback and App Development 06:02 The Role of AI in Coding 08:58 Using ChatGPT and Copilot Effectively 11:58 Navigating iOS and Xcode Updates 15:04 Exploring New Features in iPhone 16 17:58 Maui and .NET Updates 20:55 Understanding Workload Management in .NET 24:03 The Importance of Staying Updated 27:02 Building a Snack App for Disney World 30:05 Creating a Content Button in Maui 32:48 Final Thoughts and Future Plans YouTube YouTube: https://youtu.be/f9rAV9lW9tk

In this episode, Jon and Allan discuss various topics, including listener feedback, using SQLite for local data storage, changes in Android's page size, creating a personalized video for a Disney trip, and working on a marketing app with custom requirements. In this conversation, Jon and Allan discuss the challenges and best practices of using collection views and bindable layouts in mobile app development. They caution against nesting collection views and bindable layouts within each other, as it can lead to performance issues and difficulties with recycling views. They also emphasize the importance of using cancellation tokens to properly handle asynchronous operations and avoid memory leaks. The conversation concludes with a discussion on the EmbedIO plugin, which allows developers to host a local web server within their mobile apps. Takeaways Listener feedback is important and should be addressed in future episodes Using SQLite for local data storage can be a simple and efficient solution Android's change in page size will require rebuilding native libraries Creating a personalized video for a Disney trip can be a fun and memorable experience Working on a marketing app with custom requirements can be challenging but rewarding Avoid nesting collection views and bindable layouts within each other to prevent performance issues and difficulties with view recycling Use cancellation tokens to properly handle asynchronous operations and avoid memory leaks Consider alternative approaches, such as lazy loading or logical collapsing, when dealing with large datasets or complex UI structures The EmbedIO plugin allows developers to host a local web server within their mobile apps People Hosts: Jon Dick, Allan Ritchie Audio/Video Engineer: Jim Heath Chapters 00:00 Introduction and Listener Feedback 03:47 Using SQLite for Local Data Storage 12:11 Android's Change in Page Size 16:17 Creating a Personalized Video for a Disney Trip 20:12 Working on a Marketing App with Custom Requirements 31:11 Authentication Flows and Security 49:03 Challenges with Collection Views and Bindable Layouts 53:11 Avoid Nesting Scrolling Views 01:01:25 Exploring the EmbedIO Plugin YouTube: https://youtu.be/MH4bwX3JsNY

The conversation revolves around the challenges and complexities of implementing in-app purchases in mobile apps, specifically focusing on the iOS and Android platforms. The hosts discuss the history of in-app purchases, the revenue cut taken by app stores, the introduction of subscriptions, and the implementation details and testing process involved. They also touch on the limitations and changes in the APIs provided by Apple and Google, as well as the importance of proper testing to ensure a smooth user experience. The conversation discusses the challenges and frustrations of dealing with payment processors, specifically in the context of mobile app development. The hosts express their dissatisfaction with the complexity and lack of flexibility in existing payment systems, such as Apple's StoreKit and Google's Play Billing. They highlight the difficulties of implementing and maintaining payment functionality, including handling subscriptions, refunds, and different transaction states. The hosts also mention RevenueCat as a potential solution that abstracts away the complexities of payment processing and provides a more streamlined experience for developers. The conversation revolves around the challenges and frustrations of implementing in-app purchases in mobile apps. The hosts discuss their personal experiences with app stores, subscription management, and revenue cat. They also touch on the complexities of handling transactions, storing subscription data, and the limitations of the current in-app purchase systems. YouTube: https://youtu.be/cI0vf--ZQqY Takeaways In-app purchases have evolved from one-time consumables to recurring subscriptions, allowing developers to generate continuous revenue. App stores like Apple and Google take a percentage cut from in-app purchases, which can impact the profitability of developers. Implementing in-app purchases involves dealing with complex APIs, handling subscription renewals, and validating transactions. Testing in-app purchases is crucial to ensure a seamless user experience and avoid revenue loss. The APIs and implementation details for in-app purchases differ between iOS and Android, with each platform having its own challenges and limitations. Existing payment processors for mobile apps, such as Apple's StoreKit and Google's Play Billing, can be complex and inflexible to work with. Implementing and maintaining payment functionality, including handling subscriptions, refunds, and transaction states, can be time-consuming and challenging for developers. RevenueCat is a potential solution that abstracts away the complexities of payment processing and provides a more streamlined experience for developers. Having a backend service like RevenueCat handle payment processing can free up developers to focus on providing value to their users. Simplifying the payment process and providing clear documentation and examples can greatly improve the developer experience. Implementing in-app purchases can be challenging and frustrating App stores have complex rules and limitations for in-app purchases Subscription management and revenue cat can help simplify the process Handling transactions and storing subscription data require careful consideration People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Background 03:05 The Evolution of In-App Purchases 05:57 Implementing In-App Purchases: Challenges and Complexity 10:00 The Importance of Proper Testing 12:57 Differences in iOS and Android In-App Purchase APIs 24:58 The Complexity of Payment Processors 27:15 The Cost of Subscription Business 29:11 The Complexity of API Configuration 34:03 RevenueCat: Abstracting Payment Processing 36:09 Simplifying the Developer Experience 44:31 The Challenges of Implementing In-App Purchases 50:01 Simplifying Subscription Management with Revenue Cat 52:39 Handling Transactions and Storing Subscription Data

In this episode, Jon and Allan discuss various topics, including office renovations, phone migrations, and the use of mediator patterns in app development. They explore the concept of vertical slicing in architecture and the benefits of using a mediator to route messages. Allan shares his experience with mediator patterns in server architecture and highlights the need for a mediator pattern in app development. They also touch on the scalability of mediator patterns and the potential challenges of using them in certain scenarios. The conversation explores the concept of using a mediator pattern to handle services in an app. The mediator pattern allows for loose coupling and easier unit testing. It also simplifies the management of common services and reduces the need for multiple service injections. The conversation also touches on the use of events and requests with responses in the mediator pattern. The implementation of the mediator pattern in the context of a Maui app is discussed, including handling events and requests, offline mode, caching, and resiliency. In this conversation, Jon and Allan discuss the benefits and use cases of using MediatR in mobile app development. They explore the concept of middleware and how it can be used to handle various aspects of app functionality. They also discuss the challenges of finding and managing dependencies in a loosely coupled architecture. Allan introduces his MediatR library and explains how it simplifies the implementation of Mediator patterns in mobile apps. They also touch on topics like offline caching, resiliency, and event handling. Takeaways Mediator patterns can be used to vertically slice business domains in app development. Mediators act as traffic cops, directing messages to the appropriate services. Mediator patterns can improve code organization and reduce the need for injecting multiple services. Using a mediator pattern can make testing and maintaining code easier. Mediator patterns may not be suitable for high-frequency messaging or performance-critical scenarios. The mediator pattern can be used to handle services in an app, providing loose coupling and easier unit testing. Using a mediator pattern simplifies the management of common services and reduces the need for multiple service injections. Events and requests with responses are key components of the mediator pattern. The mediator pattern can be implemented in a Maui app to handle events and requests, enable offline mode, caching, and resiliency. Attributes can be used to customize the behavior of the mediator pattern, such as handling offline mode, caching, and user notifications. MediatR is a powerful library that simplifies the implementation of Mediator patterns in mobile app development. Middleware can be used to handle various aspects of app functionality, such as offline caching, resiliency, and event handling. Loosely coupled architectures can be challenging to manage, but tools like MediatR can help alleviate some of the complexity. Finding and managing dependencies in a messaging-based architecture can be difficult, but there are strategies like namespacing and code navigation that can help. MediatR provides a flexible and extensible solution for handling requests and events in mobile apps. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Office Renovations 09:07 Phone Migrations and Mediator Patterns 14:21 Understanding Mediator Patterns 17:13 Challenges of Scaling Mediator Patterns 23:04 Implementing the Mediator Pattern in a Maui App 27:59 Enabling Offline Mode, Caching, and Resiliency 41:42 Source Generation and Runtime Lookup 43:24 Replay: Handling Async Enumerables 46:04 Mediator as a Stepping Stone 48:26 Removing Attributes and Changing Behavior 52:05 Improving Developer Experience 55:11 Using Essentials API for Main Thread Handling 57:20 Offline Caching with MediatR 01:00:18 Using Middleware for Request Handling 01:02:34 Considering...

The conversation revolves around the topic of connectivity in remote areas and the use of offline apps. The hosts discuss their experiences with limited connectivity while traveling and camping. They also touch on the evolution of GPS technology and the challenges of offline mapping. The conversation highlights the importance of offline functionality in apps and the limitations of current map providers. The conversation covers various topics related to maps, offline capabilities, and communication technologies. The main themes include different map providers, the challenges of offline maps, the use of Bluetooth Low Energy (BLE) for communication, and the limitations of current location technologies. The conversation covers various topics related to offline functionality and Bluetooth technology. Allan discusses the importance of designing apps to work offline and the challenges that can arise when there is no internet connection. He also highlights the capabilities of Bluetooth 5 for data transfer and suggests using Bluetooth for offline communication when the internet is unavailable. The conversation touches on the concept of pause and resume for larger file transfers and the use of range requests in HTTP for resuming interrupted uploads. The hosts also share personal anecdotes about their experiences with slow internet connections and the use of download managers in the past. Takeaways Limited connectivity is still a common issue in remote areas, even with advancements in technology. Offline functionality in apps is crucial for users who frequently find themselves without internet access. GPS technology has come a long way, but some older devices still struggle with accuracy and reliability. Map providers like Google and Apple lack robust APIs for developers to easily implement offline maps in their apps. There are several map providers available, including ArcGIS, Google Maps, Apple Maps, Mapbox, and OpenStreetMap. Offline map capabilities are important for areas with limited internet coverage or for applications that require offline access to maps. Mapbox offers its own map tiles and also allows users to plug in different tile providers. OpenStreetMap is a community-driven project that provides up-to-date map data. Tesla cars use a combination of OpenStreetMap data and vision-based systems for features like speed limits. SVGs can be challenging to render and are not always suitable for offline use. Bluetooth Low Energy (BLE) can be used for offline communication, such as sending messages and images. Location technologies like GPS and LTE have limitations in terms of accuracy and availability. Ultra-wideband and other technologies are being explored for more precise location tracking. The nearby API by Google and the Estimote beacons are examples of technologies that enable proximity-based communication. Designing apps to work offline is important for scenarios where there is no internet connection. Bluetooth 5 can be used for data transfer even when the internet is unavailable. Range requests in HTTP can be used to resume interrupted uploads. Slow internet connections and the use of download managers were common challenges in the past. Consider using Bluetooth for offline communication and file transfers in IoT devices. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Discussion on Limited Connectivity 02:59 The Evolution of GPS Technology 08:00 Challenges with Offline Apps and Mapping 20:44 Exploring Different Map Providers 25:12 Mapbox Bindings and SVG Challenges 33:22 Importance of Internet on a Plane 36:02 Using Bluetooth Low Energy for Communication 39:00 Building a BLE Chat App for Offline Communication 41:23 Limitations of Location Technologies 44:37 Designing Apps for Offline Functionality 46:21 Resuming Interrupted Uploads with Range Requests 57:42 Challenges of Slow Internet Connections 01:03:01 Using Bluetooth for Offline Communication in IoT Devices

In this conversation, Jon and Allan discuss the upcoming features in .NET 9 and Maui. They talk about the challenges faced during the development of Maui and the improvements made in the tooling. They also discuss the new C# language features, including collection expressions and the system threading lock type. They touch on the concept of workloads and the introduction of workload version sets to improve the stability and repeatability of builds. They also mention the new title bar customization feature in Maui. In this conversation, Jon and Allan discuss several topics related to .NET MAUI. They cover the customization of the title bar, the new disconnect handlers feature, the embedding of Maui code into native apps, the upcoming CollectionView handler 2, and the potential switch to using unpackaged templates for Windows. They also mention the importance of having an escape hatch when using external libraries and the benefits of the dev loop on Windows. They conclude by encouraging listeners to leave five-star reviews and recommending the Warp tool for Mac users. Takeaways The development of Maui faced challenges, but improvements have been made in the tooling. New C# language features in .NET 9 include collection expressions and the system threading lock type. Workloads and workload version sets have been introduced to improve the stability and repeatability of builds. Maui now has a title bar customization feature for windows. The conversation highlights the importance of open and transparent communication in the development process. Customizing the title bar in .NET MAUI allows for the addition of various elements such as icons and menus. Disconnect handlers in .NET MAUI help manage memory leaks and provide control over when resources are released. The embedding feature in .NET MAUI allows developers to integrate Maui code into existing native apps. The upcoming CollectionView handler 2 in .NET MAUI will use newer APIs, improving performance and reducing complexity. There is a potential switch to using unpackaged templates for Windows in .NET MAUI, which would improve the development experience and deployment process. Having an escape hatch when using external libraries allows for flexibility and easier swapping of components. The dev loop on Windows is fast and efficient, making it a preferred platform for development. Leaving five-star reviews and recommending tools like the Warp tool for Mac users helps support the community and discover new resources. People Hosts: Jon Dick, Allan Ritchie A/V Engineer: Jim Heath Chapters 00:00 Introduction and Challenges in Maui Development 02:31 New C# Language Features in .NET 9 04:58 Workloads and Workload Version Sets 10:00 Title Bar Customization in Maui 14:20 Importance of Open and Transparent Communication 32:56 Customizing the Title Bar 39:30 Disconnect Handlers 43:35 Embedding Maui Code 49:05 CollectionView Handler 2 55:44 Switching to Unpackaged Templates for Windows 59:04 The Dev Loop on Windows 01:03:52 Having an Escape Hatch 01:05:56 Recommendation: The Warp Tool

In this conversation, Jon and Allan discuss their love for coffee and the potential for an AI-powered coffee machine. They also delve into the topic of AI and its applications, particularly in image recognition and document intelligence. Allan shares his experience with training models for forms recognition and credit card scanning, highlighting the benefits of AI in automating data extraction. They also touch on the challenges of image resolution and the potential for on-device AI models. The conversation covers topics such as on-device barcode scanning, Azure Vision, Firebase ML, multilingual apps, and the use of AI in documentation and issue management on GitHub. In this conversation, Allan and Jon discuss their experiences with source generators and AI. They talk about the challenges and benefits of using source generators in their projects and how AI can be applied in various domains. They also mention the importance of understanding the limitations and potential liabilities of AI systems. Additionally, they mention new barcode scanning packages for Maui and reflect on their past experiences with native packages. Takeaways AI can be applied to improve the coffee-making process, leading to better quality and automation. AI has made significant advancements in image recognition and document intelligence, enabling the extraction of data from various sources. Training AI models for specific tasks, such as forms recognition and credit card scanning, can greatly enhance data processing and automation. Image resolution and optimization are crucial factors in achieving accurate results with AI models. The potential for on-device AI models offers benefits such as reduced bandwidth usage and improved energy efficiency. On-device barcode scanning is available through Azure Vision and Firebase ML. Azure Document Intelligence SDK works well in Maui apps and can be used for tasks like credit card scanning. AI can be used to automate documentation writing and make it sound more professional. AI can help identify duplicate issues and provide relevant suggestions on GitHub. AI language models like ChatGPT can be used to generate code samples and improve productivity. AI language models can also be used for multilingual apps and translation tasks. Roslyn analyzers can be used to analyze and provide suggestions for code quality and best practices. Source generators can be a powerful tool for generating code and fixing issues, but they require a good understanding of the underlying syntax and tree structure. AI can be used in various domains, such as creating assistants and analyzing data, but it's important to consider the potential liabilities and ensure accurate results. New barcode scanning packages for Maui, such as 'barcode-mobile.Maui' and 'barcode-scanning.native.Maui', provide improved functionality and integration with Apple Vision and AndroidX. Understanding the limitations and potential costs of AI systems is crucial for effective implementation and user satisfaction. Reflecting on past experiences with native packages, such as ACR Dialogues and HUD, highlights the longevity and continued use of certain libraries in the development community. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 The Quest for the Perfect Cup of Coffee: AI-Powered Coffee Machines 03:21 Advancements in Image Recognition and Document Intelligence with AI 07:37 Automating Data Extraction with AI: Forms Recognition and Credit Card Scanning 11:52 Optimizing Image Resolution for Accurate AI Results 18:12 The Potential of On-Device AI Models: Efficiency and Convenience 20:40 On-Device Barcode Scanning 24:08 Azure Document Intelligence and Maui Apps 26:11 Automating Documentation Writing 37:14 AI-Powered Issue Management on GitHub 40:08 AI for Multilingual Apps and Translation Tasks 42:42 Using Roslyn Analyzers for Code Quality 42:51 Introduction 43:00 Challenges and Benefits of Source Generators 43:29 Applying AI in Various...

In this episode, Jon and Allan discuss various topics related to backend development. They start by joking about Canadian stereotypes and accents. Then, they dive into the world of backend development using ASP.NET Core and API controllers. They talk about the changes in API controllers and the use of IActionResult. They also discuss the benefits of using OpenAPI and generating contracts from it. They mention tools like Kyoto and Refit/Refitter for generating contracts and API clients. The conversation ends with a humorous remark about the possibility of a future tool called 'Refitist.' The conversation covers topics such as Refit, resiliency, GraphQL, OData, and Mediator pattern. Refit is discussed as a tool to generate code for API consumption. Resiliency is mentioned as a client-side concern, and the use of Polly for retrying failed requests is debated. GraphQL and OData are compared in terms of their usefulness and complexity. The Mediator pattern is introduced as a way to structure code and facilitate future scalability. Real-time communication with SignalR is briefly mentioned. The conversation covers topics such as real-time data streaming, the use of Docker for development and deployment, and experiences with different SQL databases. The hosts discuss the pros and cons of real-time data streaming and the various methods available. They also explore the use of Docker for local development and deployment, highlighting its benefits in creating consistent environments. The conversation then shifts to experiences with different SQL databases, including Oracle, MySQL, and SQL Server. They discuss the challenges and advantages of each database and the importance of proper database design and optimization. In this final part of the conversation, Allan and Jon discuss their experiences with different backend technologies, including Postgres SQL and backend-as-a-service platforms like Firebase and Apprite. They also touch on the challenges of managing costs and scalability in cloud services. The episode concludes with a mention of the Packages of the Week segment and a reminder for listeners to leave a five-star review. Takeaways Backend development in ASP.NET Core involves using API controllers and IActionResult. OpenAPI is a useful tool for generating contracts and defining API endpoints. Tools like Kyoto and Refit/Refitter can be used to generate contracts and API clients. The conversation highlights the importance of keeping up with changes in backend development tools and practices. Refit is a tool for generating code to consume APIs Resiliency is a client-side concern and can be handled with tools like Polly GraphQL and OData are compared in terms of their usefulness and complexity The Mediator pattern is a way to structure code and facilitate future scalability Real-time communication with SignalR is challenging for mobile apps Real-time data streaming methods vary and depend on the specific use case and requirements. Docker is a useful tool for creating consistent development and deployment environments. Different SQL databases have their own strengths and weaknesses, and the choice depends on the specific needs of the project. Proper database design and optimization are crucial for efficient and scalable applications. Postgres SQL is a reliable and fast database option with excellent driver support in .NET Backend-as-a-service platforms like Firebase and Apprite offer a comprehensive set of tools and infrastructure for building apps Managing costs and scalability in cloud services can be challenging, but it's important to find the right balance Consider leaving a five-star review for the podcast to show support and provide feedback People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Canadian Stereotypes 04:42 Exploring Backend Development 09:03 Streaming Results and OpenAI 13:52 Generating Contracts with Kyoto and Refit/Refitter 19:46 The Future of Backend Development 27:19...

The conversation revolves around the topic of drawn controls in mobile app development. The hosts discuss the pros and cons of using drawn controls versus native controls, as well as the challenges and considerations involved. They explore the idea of a hybrid approach, where some controls are drawn while others remain native. The conversation touches on topics such as scrolling, text entry, and performance implications. Overall, the hosts emphasize the importance of choosing the right approach based on the specific requirements and goals of the app. The conversation explores the challenges and considerations of drawing controls in cross-platform development. It discusses the options of using Skia or native APIs for rendering text and achieving platform-specific looks. The availability of drawing controls in MAUI is highlighted, along with the ability to choose between native drawing surfaces and SkiaSharp. The conversation also touches on the accessibility and sizing implications of drawing controls, as well as the potential benefits of easier unit testing and scalability. In this conversation, Allan and Jon discuss the challenges and considerations of using cross-platform code for drawing controls. They explore the value proposition of using libraries like Syncfusion and the trade-offs of using SkiaSharp for drawing controls. They also touch on the benefits of creating custom layouts and the potential of libraries like AlohaKit and DrawnUI for building visually appealing UIs. Takeaways There are different approaches to implementing controls in mobile app development, including drawn controls and native controls. The choice between drawn controls and native controls depends on the specific requirements and goals of the app. A hybrid approach, combining drawn controls and native controls, can provide a balance between customization and platform conformity. Challenges in implementing drawn controls include scrolling, text entry, and performance optimization. Considerations for choosing between drawn controls and native controls include design consistency, resource management, and system integration. Drawing controls in cross-platform development can be challenging due to differences in rendering text and achieving platform-specific looks. MAUI offers the option to draw controls using native drawing surfaces or SkiaSharp, providing flexibility and consistency across platforms. Accessibility and sizing considerations are important when drawing controls, as they may require additional code to ensure proper functionality. Drawing controls can simplify unit testing and improve scalability by reducing the need for maintaining abstractions over native controls. The availability of drawing controls in MAUI opens up possibilities for easier customization and design flexibility. Using cross-platform code for drawing controls can be challenging and may require additional considerations, such as accessibility APIs on each platform. There is value in using libraries like Syncfusion for existing investments and documentation, but there may be limitations and complaints about library size. Creating custom layouts can be a solution for complex UI requirements and can be achieved by measuring and laying out elements. Libraries like AlohaKit and DrawnUI offer options for building visually appealing UIs with customizable controls and layouts. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Inside Joke 01:13 Topic Introduction: Drawn Controls 07:13 Design Consistency vs. Platform Conformity 13:35 Text Entry and Customization 22:26 Scrolling and Performance Optimization 25:48 Challenges and Considerations of Drawing Controls 27:33 The Availability of Drawing Controls in MAUI 29:09 Accessibility and Sizing Implications of Drawing Controls 31:17 Simplifying Unit Testing and Improving Scalability with Drawing Controls 47:52 Introduction 48:04 Challenges and Considerations of Cross-Platform Code for...

In this conversation, Jon and Allan discuss various tools they use for development. They talk about their preferred operating systems, monitors, and IDEs. They also mention specific tools like Insomnia for API testing and DevTools for debugging. The conversation is light-hearted and includes some banter about Canadian jokes and hockey. In this part of the conversation, Jon and Allan discuss various tools they use, including antivirus software, DevToys, Setapp, file managers, Docker, Cosmos DB, and coffee brewing equipment. In this conversation, Allan and Jon discuss various soft tools and libraries that they use in their development projects. They cover topics such as coffee-making methods, microphones and audio equipment, standing desks, and .NET libraries like MVVM Toolkit, .NET Orleans, and MediatorR. They also mention the Shiny Templates, a collection of templates for Xamarin and Maui apps. Overall, they provide insights into the tools and libraries they find useful in their development workflows. Takeaways Visual Studio and Visual Studio for Mac are popular IDEs for development Insomnia is a useful tool for API testing DevTools is great for debugging Choosing the right operating system and monitor can greatly enhance the development experience Having a good set of tools can improve productivity and efficiency Antivirus software can sometimes cause issues with certain tools and applications. DevToys is a useful tool for various tasks like encoding/decoding strings and testing Xpath queries. Setapp is a subscription service that provides access to a wide range of tools and apps for Mac users. Forklift is a file browser and development toolkit for Mac. Total Commander is a file manager that offers a dual-pane interface and other advanced features. Using a proper coffee grinder, like a burr grinder, can result in a better coffee brewing experience. Chemex is a popular coffee brewing method that requires a specific type of kettle and filters. The choice of tools can greatly impact productivity and user experience in software development. There are various soft tools and libraries that developers can use to enhance their development workflows. Choosing the right tools and libraries depends on the specific needs and requirements of the project. Some popular soft tools and libraries mentioned in the conversation include MVVM Toolkit, .NET Orleans, and MediatorR. The Shiny Templates collection provides a wide range of templates for Xamarin and Maui apps. Experimenting with different tools and libraries can help developers find the ones that work best for them. People Hosts: Jon Dick, Allan Ritchie Audio/Video Engineer: Jim Heath Chapters 00:00 Introduction and Canadian Jokes 02:32 Exploring the Tools We Use for Development 09:17 Using Visual Studio and Rider for Development 13:07 Testing APIs with Insomnia 16:22 The Importance of a Good Monitor 21:07 Other Useful Tools for Development 22:30 Antivirus Software and Compatibility Issues 23:35 DevToys: A Handy Tool for Various Tasks 24:23 Setapp: A Subscription Service for Mac Users 25:24 Forklift: A File Browser and Development Toolkit for Mac 26:09 Total Commander: A Feature-Rich File Manager 29:30 Docker: Simplifying Development and Deployment 30:19 Kubernetes: A Powerful Container Orchestration Platform 31:33 Cosmos DB: Offline Development Challenges 33:19 PostgreSQL: A Versatile and Feature-Rich Database 36:16 Parallels: Efficient Virtualization for Mac 38:12 The Importance of a Proper Coffee Grinder 39:39 Brewing Coffee with Chemex: A Unique Experience 42:15 The Impact of Tools on Productivity and User Experience 43:21 The Shower Method of Making Coffee 45:36 Soft Tools for Podcasting 48:19 Microphones and Audio Equipment 49:22 Standing Desks and Key Lights 52:18 Soft Tools for Mobile App Development 55:49 MVVM Toolkit and .NET Orleans 58:11 Shiny Templates for Xamarin and Maui Apps 01:00:53 MediatorR for Modular Monoliths

In this episode, Jon and Allan discuss logging and configuration in mobile app development. They talk about their personal experiences with configuration and logging, including using environment variables, embedded resources, and external libraries like Sentry. They also touch on the performance implications of logging and the potential for source generation to improve configuration handling. Overall, they emphasize the importance of considering the specific needs of the app and the trade-offs between convenience and performance. In this conversation, Allan and Jon discuss logging and error handling in mobile app development. They mention the importance of having good logging tools and the drawbacks of using outdated tools like App Center. They also talk about the benefits of using a local logging system for debugging purposes. The conversation concludes with a discussion on the proper use of try-catch blocks and the importance of handling exceptions at the right level. Takeaways Consider the specific needs of your app when implementing configuration and logging Use environment variables or constants for simple configuration needs Be mindful of the performance implications of logging, especially in mobile apps Explore external libraries like Sentry for crash reporting and error handling Source generation can be a powerful tool for handling configuration Having good logging tools is crucial for effective debugging and error handling in mobile app development. Using outdated tools like App Center for logging can lead to code pollution and limited functionality. Local logging can be useful for debugging purposes, especially in scenarios where cloud logging is not necessary or practical. Try-catch blocks should be used strategically and not excessively. They should be placed at the event triggers or where exceptions can be handled effectively. Proper error handling and logging practices can help improve the overall stability and user experience of mobile apps. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Episode Number 06:02 Exploring External Libraries for Error Handling 11:04 Finding the Right Balance: Convenience vs Performance 23:45 Considerations for Configuration and Logging in Mobile Apps 26:11 The Performance Implications of Logging 29:12 Logging and Performance: A Closer Look 32:05 The Drawbacks of Using Outdated Logging Tools 34:12 The Benefits of Local Logging 36:26 Strategic Use of Try-Catch Blocks 41:38 Proper Error Handling and Logging Practices

The conversation covers various mobile app development pitfalls and best practices, including the use of assembly scanning, loading large JSON files, and the misuse of dependency injection. The hosts share their experiences and insights on these topics, highlighting common mistakes and potential solutions. The conversation covers topics related to app performance, dependency injection, service management, constructor logic, and the impact of changes from Xamarin Forms to Maui. It delves into the challenges of resolving services, the use of async calls in constructors, and the importance of separating concerns in service management. The discussion emphasizes the need for thoughtful design and the avoidance of unnecessary complexity. In this conversation, Allan and Jon discuss the challenges and misconceptions surrounding observable collections in app development. They explore the performance implications, misuse, and alternative solutions, as well as the complexities of source generators and incremental generators. The conversation also touches on the importance of learning from mistakes and the potential for Roslyn analyzers in XAML. The episode concludes with a discussion about a new plugin package and listener feedback. Takeaways Mobile app development often involves common pitfalls and best practices that developers should be aware of. Assembly scanning and loading large JSON files can impact app performance and should be approached with caution. Misuse of dependency injection, such as making pages singleton for faster loading, can lead to unexpected issues and should be carefully considered. Source generators can be a valuable tool for optimizing app performance and reducing unnecessary code. Understanding the implications of various development practices is crucial for creating efficient and reliable mobile applications. App performance can be impacted by the management of services and the logic within constructors. Separating concerns in service management is crucial for maintaining code quality and performance. The transition from Xamarin Forms to Maui introduces changes that can affect app performance and behavior. Avoiding unnecessary complexity and thoughtful design are key principles for effective service management and app performance optimization. Observable collections can lead to performance issues and are often misused in app development. Source generators and incremental generators present complexities and challenges in app development. Learning from mistakes is an important part of growth and improvement in software development. Listener feedback and engagement are valuable for shaping future podcast episodes and content. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Nostalgic Reflections 02:50 Common Pitfalls in Mobile App Development 24:22 Dependency Injection Best Practices 42:27 The Impact of Xamarin Forms to Maui Transition 48:53 Constructor Logic and Service Resolution Challenges 51:29 Challenges of Observable Collections in App Development 54:14 Learning from Mistakes in Software Development 01:05:30 Engaging with Listener Feedback

The conversation delves into the topic of dependency injection (DI) and its evolution over the years. It covers the history of DI, different DI libraries, considerations for mobile development, and the future of DI with source generation. The discussion also touches on performance optimizations and the impact of DI on app startup time. The conversation covers topics related to dependency injection, scoping mechanisms, and the challenges of managing scopes in Maui apps. It also delves into the use of Prism and the need for out-of-the-box conventions for handling life cycles and navigation services in Maui. The conversation covers a deep dive into dependency injection, scope boundaries, and the challenges of managing dependencies in the context of mobile app development. It also delves into the nuances of using different DI containers and the impact on app performance. The hosts share their experiences, insights, and recommendations for handling these complexities effectively. Takeaways Dependency injection has evolved over the years and has become a crucial part of app development, especially in the mobile space. Different DI libraries have their own strengths and considerations, and the choice of library depends on the specific use case and performance requirements. The future of DI may involve source generation, which could lead to significant improvements in performance and reduce complexity in the registration process. Considerations for mobile development include the impact of DI on app startup time and the need for performance optimizations. Property injection and constructor injection are both relevant approaches in DI, and the choice between them depends on the specific requirements of the application. Understanding the challenges of managing scopes in Maui apps The need for out-of-the-box conventions for handling life cycles and navigation services in Maui Insights into the use of Prism and its impact on dependency injection in Maui apps Understanding scope boundaries is crucial for effective dependency injection in mobile app development. Choosing the right DI container can significantly impact app performance and memory management. Managing dependencies and understanding scope lifetimes is essential for avoiding memory leaks and performance issues in mobile apps. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapter 00:00 The Evolution of Dependency Injection 07:18 Considerations for Mobile Development 13:47 The Future of Dependency Injection 23:23 Understanding Scoping Mechanisms and Life Cycles 26:34 The Need for Out-of-the-Box Conventions in Maui 29:04 Dependency Injection and Prism in Maui Apps 41:28 Understanding Scope Boundaries in Dependency Injection 43:21 Common Misconceptions about Dependency Injection 45:23 Impact of Dependency Injection in Prism and Maui Apps 47:11 Debugging and Validation in Dependency Injection 53:45 Audio Quality and Listener Engagement

In this conversation, Jon and Allan discuss various topics related to architecture and performance in mobile app development. They touch on the challenges of implementing the MVVM pattern and the potential for excessive property changed notifications. They also discuss the use of observable collections and the importance of using them only when necessary. Additionally, they express their dislike for messaging services and suggest using events or actions instead. Overall, the conversation emphasizes the need for thoughtful architecture and optimization in mobile app development. The conversation explores the use of mediator pattern in mobile and app development. The mediator pattern is seen as a solution to prevent service overrun and to provide logical separation in the app. It allows for vertical slicing of concerns and prevents the need for injecting multiple services. The conversation also discusses the challenges of messaging services and the benefits of using a mediator pattern in terms of scalability, error handling, and unit testing. The potential application of the mediator pattern in Xamarin and .NET Maui apps is explored. In this conversation, Allan and Jon discuss the concept of using a mediator pattern in mobile app development. They explore the benefits of using a mediator to handle communication between different components of an app, such as view models and services. They also discuss existing implementations of the mediator pattern, such as MediatR, and potential future developments in this area. Overall, they highlight the potential value of using a mediator pattern in mobile app architecture. Takeaways Implementing the MVVM pattern can lead to excessive property changed notifications, which may impact performance. Observable collections should be used only when data is constantly changing, such as in real-time applications. Consider using events or actions instead of messaging services for better control and clarity in event handling. Thoughtful architecture and optimization are crucial for improving performance in mobile app development. The mediator pattern can be a solution to prevent service overrun and provide logical separation in mobile and app development. Using a mediator pattern allows for vertical slicing of concerns and prevents the need for injecting multiple services. The mediator pattern offers benefits such as scalability, error handling, and ease of unit testing. The potential application of the mediator pattern in Xamarin and .NET Maui apps is worth exploring. The mediator pattern can be a valuable tool for handling communication between different components of a mobile app. Using a mediator can simplify unit testing by allowing developers to focus on testing individual components rather than the entire app. Existing implementations of the mediator pattern, such as MediatR, can provide a solid foundation for incorporating this pattern into mobile app development. The mediator pattern can help clean up code and improve the organization and separation of concerns in mobile app architecture. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Personal Updates 03:00 Challenges of Implementing the MVVM Pattern 09:04 Optimizing the Use of Observable Collections 14:57 Avoiding Excessive Messaging Services 22:18 Challenges with Messaging Services 24:02 Exploring the Mediator Pattern 27:07 The Role of Mediators in Routing 30:17 Separation of Concerns and Dependency Injection 33:30 Handling Events in Temporary View Models 36:00 Benefits of the Mediator Pattern 40:08 Scaling and Breaking Down Hotspots 44:20 Command Handlers and Mediator Interaction 46:27 Focusing on the Action with Mediators 49:28 Simplifying Unit Testing with a Mediator 52:17 Existing Implementations of the Mediator Pattern 55:11 Handling Unsolicited Notifications with a Mediator 57:24 Mediator Libraries and Best Practices 01:00:57 Challenges and Considerations for Mediator Implementation...

In this conversation, Jonathan discusses his experience with building automation control systems for his swimming pool using microcontrollers and IoT devices. He talks about controlling the pool temperature, pool pumps, and a saltwater generator. He also explores the challenges and considerations of using different microcontrollers, such as the ESP8266 and the Meadow board, which runs .NET. Jonathan shares his passion for building IoT projects and the potential for using favorite programming languages in these environments. The conversation covers various topics related to IoT platforms, including the evolution of hardware into software-as-a-service (SaaS) platforms, the expansion of Meadow's ecosystem, the integration of Raspberry Pi with Meadow, the challenges of running web servers on microcontrollers, and personal projects involving IoT devices. The conversation also touches on the use of Meadow in pool automation and coffee brewing, as well as the ingenuity of building custom solutions using sensors and Raspberry Pi. Takeaways Building automation control systems for swimming pools using microcontrollers and IoT devices is a fascinating and practical application of technology. Controlling the pool temperature, pool pumps, and other aspects of pool maintenance can be automated using microcontrollers and relays. Different microcontrollers, such as the ESP8266 and the Meadow board, offer various capabilities and programming options for building IoT projects. The Meadow board, which runs .NET, provides a more familiar programming environment for developers and offers the potential for using favorite programming languages in IoT - projects. IoT platforms often evolve from hardware devices to full-fledged software-as-a-service (SaaS) platforms. Meadow is building an ecosystem around its platform, expanding its libraries and compatibility with devices like Raspberry Pi. Running web servers on microcontrollers like Meadow can be challenging, but Meadow provides solutions like BLE servers and basic web server functionality. Personal projects involving IoT devices can range from pool automation to coffee brewing, and can be built using sensors and Raspberry Pi. Building custom solutions using sensors and Raspberry Pi can be a creative and practical way to solve real-world problems. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Background 02:26 Interest in IoT and Microcontrollers 03:50 Comparing IoT to Early Xamarin Days 08:11 Controlling Pool Temperature with Microcontrollers 09:37 Automating Pool Pumps and Saltwater Generator 28:27 Exploring the Meadow Board and .NET in IoT 33:19 The Evolution of IoT Platforms 34:41 Building an Ecosystem and Extending Compatibility 35:10 Challenges of Running Web Servers on Microcontrollers 39:23 Personal Projects: Pool Automation and Coffee Brewing 52:59 Meadow Desktop: Coding Against APIs and Simulating Graphics 01:03:38 Building Custom Solutions with Sensors and Raspberry Pi

The conversation discusses the importance of structuring apps in terms of business requirements and how to make them easier to navigate and understand. It emphasizes the need to focus on translating business requirements into technology and suggests organizing projects based on business logic rather than technology layers. The conversation also touches on the use of services and the benefits of grouping them by section or feature. Additionally, the conversation explores the challenges of using IL manipulators and the limitations of certain frameworks in the context of C# hot reload. It concludes with a discussion on the need for base implementations and templates that provide guidance on structuring apps and implementing MVVM patterns. In this conversation, Jonathan and John discuss the importance of structuring services in mobile app development. They explore the use of MVVM frameworks like Prism and the challenges of writing technical code on top of existing tech services. They also discuss the benefits of using events and observables in services, as well as the use of dependency injection and the Microsoft implementation. The conversation concludes with a recommendation for the Refit library as the plugin packager product of the week. Takeaways Organize projects based on business logic rather than technology layers Group services by section or feature to improve discoverability Be cautious when using IL manipulators in mobile apps Consider the limitations of certain frameworks in the context of C# hot reload Provide base implementations and templates to guide app structure and MVVM implementation Structuring services in mobile app development is crucial for maintaining code organization and scalability. MVVM frameworks like Prism provide a comprehensive structure for building full-featured apps. Writing technical code on top of existing tech services can lead to complexity and bugs. Using events and observables in services can simplify communication between components and reduce code duplication. Dependency injection is a powerful tool for managing service dependencies and improving testability. The Refit library is a recommended tool for generating HTTP clients from interfaces in a clean and efficient way. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction 00:59 Challenges of App Layout 01:27 Discoverability of Business Logic 03:18 Organizing Projects by Business Logic 04:47 Grouping Services by Section 06:44 Considerations for Global Services 08:42 Moving Services to Relevant Folders 10:03 Multiple Implementations of Services 13:18 Challenges of IL Manipulators and C# Hot Reload 19:07 Importance of Base Implementations and Templates 00:12 Introduction 00:29 Structuring Services in Mobile App Development 34:20 The Benefits of Using Events and Observables in Services 39:43 Dependency Injection and the Microsoft Implementation 53:07 Plugin Packager Product of the Week: Refit 01:03:36 Conclusion

Jon and Allan discuss their experiences and excitement surrounding tech conferences like WWDC and Google IO. They reminisce about attending conferences in the past and the thrill of new announcements and hardware giveaways. They also speculate on what they hope to see at upcoming conferences, such as immersive movies and a foldable iPhone. The conversation touches on the evolution of UI design and the convenience of using smartphones as cameras. The conversation covers topics such as foldable phones, APIs, UI changes, app stores, and permissions. The hosts discuss their preferences for foldable phones and the potential impact on UI design. They also explore the idea of integrating AI and context awareness into app development. The conversation touches on the App Store fees and the review process. They express their frustrations with Android permissions and suggest improvements for a more streamlined process. The conversation covers various topics including the challenges of changing APIs, the user experience of notifications on different platforms, the potential for new features in Apple TV, the power of Apple's M-series chips, the future of gaming on ARM-based devices, and a shout-out to Gerald Versluis and his packages. Takeaways Tech conferences like WWDC and Google IO are exciting events for developers and tech enthusiasts. Attending conferences provides opportunities to learn about new announcements and interact with engineers. The early days of conferences were filled with groundbreaking announcements and new hardware. The current conference landscape is less surprising, but still offers valuable insights and updates. The hosts express their hopes for future conferences, including immersive movies and a foldable iPhone. The convenience and quality of smartphone cameras have made dedicated cameras less necessary. Foldable phones have advantages in terms of screen size and potential for improved UI experiences. APIs can be used to integrate AI and context awareness into app development. The App Store fees are a topic of debate, but the convenience and services provided by the platform are valuable. Android permissions can be complex and could benefit from a more unified and streamlined approach. - Changing APIs can be challenging, especially when they are frequently updated. The user experience of notifications varies between platforms, with Android offering more customization options. Apple TV could benefit from new features and updates. Apple's M-series chips are powerful and efficient, but their graphics capabilities for gaming are still uncertain. Gaming on ARM-based devices may require cloud streaming to achieve AAA game performance. Gerald Versluis has developed useful packages, such as a screenshot API and an audio plugin, that fill gaps in functionality. New features and APIs may be introduced through plugins before being integrated into cross-platform frameworks like Maui. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Discussion of Fun Topics 07:30 The Excitement of Early Conferences 26:38 App Store Fees and Review Process 45:08 Navigating the Challenges of Changing APIs 52:05 The Power and Uncertainty of Apple's M-series Chips 59:59 Shout-out to Gerald Versluis and His Useful Packages

The conversation covers topics related to coffee-making methods and the use of XAML in app development. The hosts discuss their preferences for coffee machines and the process of making coffee. They also delve into the use of converters in XAML and the debate between putting logic in the view model or the view. The conversation explores the use of converters, extensions, and behaviors in XAML and their potential drawbacks. It also discusses the benefits of using compiled bindings and the importance of declaring data types in XAML for improved performance. The conversation touches on the use of XAML in Blazor and the potential future of XAML in web development. In this conversation, Jon and Allan discuss various optimization techniques for Xamarin.Forms and .NET MAUI apps. They cover topics such as compiled bindings, the performance impact of converters in collection views, optimizing XAML layouts, and the use of third-party libraries like Sharpnado CollectionView. They also touch on the challenges of building responsive layouts and the importance of considering platform-specific optimizations. Overall, the conversation provides valuable insights into improving the performance of Xamarin.Forms and .NET MAUI apps. Takeaways There are different preferences for coffee-making methods, from simple machines like Keurig to more complex ones like Chemex. XAML can be verbose, and there is a debate about whether to put logic in the view model or the view. Converters in XAML can be useful for transforming data, but it's important to avoid excessive use and keep business logic separate. Localization in XAML can be done using dictionary strings and bindings, without the need for extensions. The use of AI for auto-localization and translation is an interesting possibility. In some cases, it may be beneficial to handle certain UI-related tasks in the view, even if it goes against the purist approach of separating concerns. Converters, extensions, and behaviors in XAML can be powerful but should be used judiciously and not overused. Compiled bindings and X-bind can be alternatives to converters and provide better performance. Declaring data types in XAML can improve performance and enable better IntelliSense. XAML can be used in Blazor, but the heavier the reliance on XAML, the more challenging it may be to migrate to Blazor. The future of XAML in web development is uncertain, with the web being the dominant platform. Compiled bindings can significantly improve the performance of Xamarin.Forms and .NET MAUI apps by eliminating the need for runtime reflection. Converters in collection views can introduce performance overhead, especially when used extensively. It's important to minimize their usage and consider alternative approaches. Optimizing XAML layouts involves avoiding unnecessary nesting of controls, using bindable grids instead of content views, and being mindful of the performance implications of stack layouts and scroll views. Third-party libraries like Sharpnado CollectionView can provide additional performance optimizations and features for collection views in Xamarin.Forms and .NET MAUI apps. Building responsive layouts can be challenging, and platform-specific optimizations may be necessary to achieve optimal performance. Consider leaving a review on Apple Podcasts and checking out the Gone Mobile YouTube channel for more content. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 The Art of Coffee-Making: From Keurig to Chemex 09:39 The Power and Pitfalls of Converters in XAML 35:28 The Power of Compiled Bindings and X-bind in XAML 45:21 Challenges of Migrating XAML-heavy Apps to Blazor 55:17 Challenges of Building Responsive Layouts 01:04:59 Leaving Reviews and Exploring the Gone Mobile YouTube Channel

The conversation revolves around the topic of offline battle tactics in mobile app development. Jon shares his experience with a pool app that required offline data storage and syncing. He initially used Realm, but faced issues with performance and scalability. He had to rewrite the login service and migrate data to a new backend. Allan discusses the challenges of offline data syncing, including handling deletes and updates, resolving conflicts, and ensuring data security. Jon explains his approach of using Cosmos DB and simple record types to handle offline data syncing. They emphasize the importance of considering the specific needs of the business and avoiding over-engineering solutions. The conversation explores the challenges and considerations of implementing offline functionality in mobile apps. The concept of 'end scars' is introduced, referring to the need to delete or reassign child data when the parent data is modified or deleted. The importance of handling offline scenarios gracefully and providing clear feedback to users is emphasized. The conversation also touches on the use of frameworks and abstractions for offline sync, with a discussion of Azure Mobile Apps and the limitations of such solutions. The benefits of using SQLite and the JSON support it offers are highlighted. In this final part of the conversation, Jon and Allan discuss their experiences with SQLite and offline functionality in mobile apps. They talk about the importance of optimizing app startup time and how SQLite can be a bottleneck in this process. They also share their preference for using SQL and the benefits of using SQLite-PCL-NET. The conversation then shifts to offline functionality and device-to-device communication, with Jon sharing his experience with Google's SDK for nearby communication. They briefly touch on the challenges of offline functionality in airplane environments and the limitations of Bluetooth connectivity. The episode concludes with a discussion on the importance of the SQLite raw library and its role in enabling advanced features like geolocation. Takeaways Offline data syncing in mobile app development can be challenging and requires careful consideration of business needs. Choosing the right technology for offline data storage and syncing is crucial for performance and scalability. Handling deletes, updates, conflicts, and data security are important aspects of offline data syncing. Simplifying the data model and using simple record types can make offline data syncing easier to implement and maintain. Avoid over-engineering solutions and focus on meeting the specific needs of the business. Offline functionality in mobile apps requires careful consideration and handling of data synchronization. Handling 'end scars' is crucial, ensuring that child data is properly managed when parent data is modified or deleted. Providing clear feedback to users about offline status and data synchronization is essential for a good user experience. Using frameworks and abstractions for offline sync may have limitations and can lead to loss of control over data management. SQLite is a reliable and widely-used option for local offline storage, with the added benefit of JSON support for flexible data storage. Optimizing app startup time is crucial, and SQLite can be a bottleneck in this process. Using SQL and libraries like SQLite-PCL-NET can provide more control and flexibility in working with databases. Offline functionality and device-to-device communication are important considerations in mobile app development. The challenges of offline functionality in airplane environments include limited connectivity options and the need for peer-to-peer networks. The SQLite raw library, maintained by Eric Sink, is a foundational piece for many SQLite-based solutions and enables advanced features like geolocation. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Setting the Stage 01:43 Offline Battle...

The conversation covers various topics related to MSBuild and project files. It starts with an introduction and a discussion about the weather. The hosts then delve into the history and evolution of MSBuild, including the transition to SDK style projects. They explain the structure of new project files and highlight the benefits of using CS Proj for managing NuGet packages and CI. The conversation also covers customizing project files for platform-specific assets and the use of conditions in project files. The hosts discuss the importance of workloads and the rationale behind different SDKs. They also touch on the future of workloads and the challenges associated with them. This conversation explores various aspects of MSBuild, including workloads, importing MSBuild from NuGet packages, building custom entitlements, adding items to build from NuGet packages, customizing build props and targets, writing custom MSBuild tasks, using custom tasks and source generators, incremental source generation, and Michaela's MSBuild Editor Extension. The hosts emphasize the importance of understanding MSBuild and encourage listeners to explore and experiment with CSProj files to optimize their build processes. Takeaways MSBuild is a powerful tool for managing project files and building applications. SDK style projects provide a more streamlined and approachable format for project files. CS Proj files can be customized to include platform-specific assets and configurations. Using CS Proj for managing NuGet packages and CI can simplify the development process. Workloads in MSBuild provide a way to manage and organize project dependencies and configurations. MSBuild is a powerful build system that allows for customization and automation of the build process. Importing MSBuild from NuGet packages provides an easier way to test nightly builds and service releases. Customizing build props and targets allows for fine-grained control over the build process and the inclusion of specific assets. Writing custom MSBuild tasks in C# can be a powerful way to extend the build system and perform complex build operations. Using custom tasks and source generators can enhance the build process and improve performance. Mikayla's MSBuild Editor Extension provides helpful features like IntelliSense and package version management for CSProj files. People Hosts: Jon Dick, Allan Ritchie Audio Engineer: Jim Heath Chapters 00:00 Introduction and Weather 00:20 Introduction to MSBuild 01:12 Acquiring Taste for MSBuild 03:17 Slim CS Proj 04:03 Structure of New Project Files 05:12 Default Maui Project Template 06:36 Using CS Proj for NuGet Packages 07:56 Benefits of Using CS Proj for CI 08:26 Customizing Project Files for Platform-Specific Assets 09:53 Leveraging MSBuild for Customization 10:57 Command Line vs. CS Proj 11:33 Importing Files and Directory Build Props 12:37 Multiple SDK Imports 13:15 Properties and Item Groups in Project Files 14:05 Conditions in Project Files 19:48 Rationale for Different SDKs 22:19 Directory Build Props for Performance 24:07 Workloads and SDK Imports 26:17 Future of Workloads 29:08 Challenges with Workloads 31:09 MSBuild and Workloads 32:03 Importing MSBuild from NuGet Packages 33:12 Custom Entitlements and Build Props 34:09 Building Custom Entitlements 36:29 Adding Items to Build from NuGet Packages 37:38 Automatically Making Apps Work with Libraries 38:36 Customizing Build Props and Targets 39:40 Doing Build-Related Tasks in MSBuild 42:10 Writing Custom MSBuild Tasks 44:23 Using Custom Tasks and Source Generators 46:19 Incremental Source Generation 49:46 Michaela's MSBuild Editor Extension 56:19 Getting Started with MSBuild