Blog

In this post, I’d like to show a simple, free, and open-source solution for using 100% offline vector maps in an iOS application. The complete source code for my playground is available on GitHub , so I won’t cover the implementation details here. Instead, this post focuses on the overall technology stack, explains how the components fit together, and provides links to all of the tools and resources you’ll need. Technology Stack iOS Map Library Vector Tile Schemas Map Styles Download OpenStreetMap Data Generate MBTiles from .osm.pbf How Everything Fits Together To avoid confusion, here’s how the individual pieces work…

In this article, I would like to cover technical specifics related to SwiftData schema updates and the unit testing of data migration. Understanding iOS Application Updates Let’s start with some specifics regarding iOS application updates: Goals for Project Structure and Testing Solution Required Procedures To achieve these goals, we should: Implementation The complete source code for this project is available on GitHub:: Example Project Schemas: Migration plans: Types: Note: You cannot migrate back to the same schema even if it is redefined with a new schema version. SwiftData calculates the schema fingerprint based on models and their fields; it…

In this article, I would like to cover live location updates while an iOS application is in the background. How they are different from usual in-app updates, what changes need to be made to the project, and some techniques to make our lives easier. Project Setup Let’s start with the setup steps that are required for an iOS project to be able to get location updates in the background. Project Info (Plist) Project > Info We need to add the privacy explanation strings: Note: Two are required because the process of acquiring consent for ‘Always’ mode is a two-step process;…

When building apps that rely on external WebServices, developers typically face the challenge of how to test and preview features without relying on a live production environment. Standard approaches usually involve maintaining a dedicated development server or creating complex “faked” service instances. While both are valid, they often introduce significant overhead and architectural boilerplate.An elegant alternative or/and addition is to fake network responses at the URLSession level. This approach moves the mocking logic outside of your specific API clients, keeping your architecture lean and allowing you easily to simulate API behaviors that aren’t even live in production yet. Setup Note:…

Introduction In this post, I explore the problem of building an architecture for small-scale projects. My main goal is to build a super simple architecture that is easy to follow and adapt. It should work out of the box for unit testing, UI testing, and previews. Furthermore, in situations with unresolvable limitations, it should be easy to refactor. Architecture Goals Architecture Global Shared Data Providers and Services This is likely the only controversial part of this architecture. I plan to access data providers and services directly from a global shared object. In a standard enterprise environment, this might be considered…