Forem: Kurt Frey

Writing and Running Swift Code without Xcode on Mac and Windows

Kurt Frey — Sun, 31 Dec 2023 08:14:22 +0000

Swift has quickly become my favourite programming language. Its sleek syntax and fail safe features (guard and if let) are beautiful. My first steps with Swift were a few years back when I made my first iOS app. I knew that Objective-C was too different from what I knew at that time and I heard good things about Swift's learning curve.

But now I wanted something more light-weight than Xcode for quick, un-sandboxed scripts. And so I looked into Visual Studio Code and Swift.

Turns out, writing a command line swift App can easily be done on macOS, Linux and Windows with VS Code, some extensions and just a few dependencies. Follow along to see how it's done.

macOS

Firstly, install Xcode or the Xcode command line tools. I recommend installing the package manager brew (homebrew). It installs Xcode command line tools for you and comes in handy when you install software that's not in the App Store (and even if it is!).

Now, install Visual Studio Code (if you haven't already) and the executable SwiftLint (which is used by the extension we'll install in a second) with i.e. brew install visual-studio-code swiftlint.

In VS Code, install the following extensions (via GUI or command line):

After that open a folder, and create a new swift project in VS Code. That's easy, because you installed the Swift Project Creation extension. In the Sources directory, there's a main.swift. Happy Coding. Once your code is ready to run, run it with a touch on the play button (or the play button with the critter for debugging) in your Touch Bar or with Run > Start Debugging (F5).

Windows

On Windows, things are a bit more involved but still straight forward once you know the culprits.

First, you'll need Visual Studio Community (at the time of writing this blogpost, Visual Studio 2022 is the most recent version). Get it via winget install --id=Microsoft.VisualStudio.2022.Community -e , or directly via Visual Studio Community if you don't have winget installed. winget (winget) is a package manager for Windows like chocolatey and scoop. They have been compared numerous times.

Don't worry, you'll still be using Visual Studio Code but Visual Studio must be installed!

If you hadn't have the chance to install the "Desktop Development with C++" component with the IDE itself, install it in Visual Studio Community, install as described here.

Next, install Swift for Windows. Also, you'll need Python 3.9 for the Swift Toolchain to work. LLDB is very picky about the Python version. Install both by using winget install Swift.Toolchain Python.Python.3.9.

Lastly, you'll need the following Visual Studio Code extensions (via GUI or command line):

Note: SwiftLint - the executable required by the extension - is not available on Windows. So we omit the extension as well.

In Windows, you have to check Swift > Debugger: Use Debug Adapter From Toolchain in the Settings of the Swift VS Code Extension.

After that open a folder, and create a new Swift project in VS Code. That's easy, because you installed the Swift Project Creation extension. In the Sources directory, there's a main.swift. Happy Coding. Once your code is ready to run, run it with Run > Start Debugging (F5).

Linux

Help me, make this blog post complete: What are your instructions for making Swift and VS Code work on Linux?

Target Platform

For targeting the most recent macOS you have to add or change the code in Package.swift to include this snippet:

platforms: [
    .macOS(.v14)
],

Otherwise there will be errors if you use a language feature that is not available in the macOS version set in Package.swift.

Remarks

Swift Versions on macOS

One disadvantage of Swift is how Apple decided to deploy new versions. They only come bundled with new versions of their operating systems. However, with swiftenv (kylef/swiftenv) other versions than the bundled one can be installed. So maybe that adds a possibility to run more modern swift versions on older hardware?

VS Code Sync

VS Code can sync settings and installed extensions. If you're running this setup on both, a macOS and a Windows machine, you'll run into troubles:

CodeLLDB has a setting that points to the lldb library. Don't sync this setting.
SwiftLint is not available on Windows. Don't sync this extension.

Transition from App Delegate to SwiftUI life cycle

Kurt Frey — Sun, 11 Sep 2022 11:00:53 +0000

Apple introduced the new SwiftUI life cycle some years ago. I still had some apps that used UIKit and the App Delegate life cycle.

Transitioning from one to the other seems trivial at first, makes you scratch your head shortly later only to realise that it actually is quite trivial.

Before you start you should redesign your views in SwiftUI and create a YourSwiftUIView which serves as the first view your users are presented with.

Firstly, remove @UIUIApplicationMain from your AppDelegate class.

Secondly, create a SwiftUI App struct:

import Foundation
import SwiftUI

@main
struct yourAppName: App {
        // Relevant if you use CoreData
    let persistenceController = PersistenceController.shared

    var body: some Scene {
        WindowGroup {
            YourSwiftUIView()
                    // Relevant if you use CoreData
                .environment(\.managedObjectContext, persistenceController.container.viewContext)
        }
    }
}

Thirdly, remove UIApplicationSupportsMultipleScenes key from your InfoPlist. This key will have quite an entourage. Remove it all.

<dict>
    <key>UIApplicationSupportsMultipleScenes</key>
    <false/>
    <key>UISceneConfigurations</key>
    <dict>
        <key>UIWindowSceneSessionRoleApplication</key>
        <array>
            <dict>
                <key>UISceneConfigurationName</key>
                <string>Default Configuration</string>
                <key>UISceneDelegateClassName</key>
                <string>$(PRODUCT_MODULE_NAME).SceneDelegate</string>
                <key>UISceneStoryboardFile</key>
                <string>Main</string>
            </dict>
        </array>
    </dict>
</dict>

Finally you can remove all the Storyboard Files and accompanying ViewControllers.

Adding Sexual Activity to Apple Health via HealthKit

Kurt Frey — Fri, 26 Aug 2022 12:40:51 +0000

There are many examples on how to add heart rate or step counts to Apple Health via HealthKit. I made an app that lets you track your sexual activity. And now I'd like to add HealthKit support.

Prerequisites

After creating the app in Xcode, add the HealthKit capability and add the string to your Info.plist.

For clarity and better practice we'll create a class that'll handle the connection to HealthKit. You could add this to a view too. It would be ugly.

Sample vs. Object

A sample is what is written to HKHealthStore and an object is what is read from HKHealthStore.

`HealthConnector`

The custom HealthConnector class facilitates interaction with HKHealthStore. It currently has two three functions:

requestAuthorization
saveSample
deleteObject

Request authorization

Before any interaction with HKHealthStore we must ask for permission. It's not enough to ask once. The user could revoke permission when we're not looking.

You have to specifically ask for the Sample Types you'd like to read from and write to. Since my app only writes samples but won't retrieve anything, requestAuthorization's read-parameter is nil.

/// This function requests permission to read and/or write to a specific
/// `HKObjectType`.
/// - Parameter completion: Completion handler must be able to handle boolean return.
func requestAuthorization(completion: @escaping (Bool) -> Void) {
    // Check if `HKHealthStore` is available to the user of the app.
    guard HKHealthStore.isHealthDataAvailable() else {
        completion(false)
        return
    }

    // Check if category type `.sexualActivity` is available to the user.
    guard let sexualActivityType = HKObjectType.categoryType(forIdentifier: .sexualActivity) else {
        completion(false)
        return
    }

    // Create a set containing the category types we'd like to access.
    let writeTypes: Set = [
        sexualActivityType
    ]

    // Finally request authorization.
    HKHealthStore().requestAuthorization(toShare: writeTypes, read: nil) {
        (success, _) in
        completion(success)
    }
}

Save a sample

/// This function saves a new sample to `HKHealthStore`. It adds all neccessary meta date.
/// - Parameters:
///   - protection: Was protection used?
///   - date: When was the date of sexual acitivty?
///   - identifier: A UUID that allows to delete the sample later.
///   - completion: Completion handler must be able to handle boolean return.
func saveSample(with protection: Bool, date: Date, identifier: UUID, completion: @escaping (Bool) -> Void) {
    // Check if category type `.sexualActivity` is available to the user.
    guard let sexualActivityType = HKObjectType.categoryType(forIdentifier: .sexualActivity) else {
        completion(false)
        return
    }

    /**
     Create the sample.
     `value` must be 0. Otherwise the app will crash.
     `metadata` must contain all three keys. `HKMetadataKeySyncIdentifier` requires `HKMetadataKeySyncVersion`. Version number is 
     */
    let sample = HKCategorySample(
        type: sexualActivityType,
        value: 0,
        start: date,
        end: date,
        metadata: [
            HKMetadataKeySexualActivityProtectionUsed: protectionUsed,
            HKMetadataKeySyncIdentifier: identifier.uuidString,
            HKMetadataKeySyncVersion: 1
        ]
    )

    HKHealthStore().save(sample) { (success, error) in
        completion(success)
    }
}

Delete an object

/// Deletes the sample with the specified identifier.
/// - Parameters:
///   - identifier: The UUID used to save the sample.
///   - completion: Completion handler must be able to handle boolean return.
func deleteObject(identifier: UUID, completion: @escaping (Bool) -> Void) {
    // Narrow down the possible results.
    let predicate = HKQuery.predicateForObjects(
        withMetadataKey: HKMetadataKeySyncIdentifier,
        allowedValues: [identifier.uuidString]
    )

    // Delete all the objects that match the predicate, which should only be one.
    HKHealthStore().deleteObjects(of: HKCategoryType(.sexualActivity), predicate: predicate) { success, _, error in
        completion(success)
    }
}

Modify a sample

You'll have to delete the old object and save a new sample.

Wrapping my head around CoreData and CloudKit

Kurt Frey — Thu, 25 Aug 2022 13:01:45 +0000

This blog post was also published on https://www.nitricware.com

If I got anything wrong, please leave a comment!

I like to understand things that wrapper and APIs like to obfuscate. CoreData especially in combination with CloudKit was very overwhelming for me. And it still is. However I could clear some things up for me.

Since I preferred Apple doing some heavy lifting, posts and tutorials that "built the whole Core Data Stack from scratch" confused me. I wanted to understand and expand what was already there.

Prepare your app for CoreData in iCloud

Create a new application and check "use CoreData" and "host in iCloud"

OR (assuming the app already uses CoreData, because if not you'd have to add the whole PersistenceController)

Replace NSPersitentContainer in PersistenceController with NSPersitentCloudKitContainer
Add container.viewContext.automaticallyMergesChangesFromParent = true in PersistenceController.init() as the last line
In "Signing & Capabilities" add for each target:
1. Background Modes: Remote Notifications
2. iCloud: CloudKit and activate the checkbox next to the container for your app (create a new one with + if needed) - you could also use an existing one and share data between apps.

You're done.

Attention: iCloud sync in simulator is wonky at best. Use physical devices.

What is an iCloud container?

An iCloud container simply put is like a directory in iCloud where all the cloud stuff of your app reside. You're using an NSPersitentCloudKitContainer? It's synced to the iCloud container. Using multiple? A single one with multiple configurations? They're all there.

The iCloud container is like the sandbox of the app on the device but in the cloud.

What is a `NSPersistentContainer`

An NSPersistentContainer is a class that handles all your interaction with a database (or multiple database files, see: configurations).

What is an `NSPersistentCloudKitContainer`

An NSPersistentCloudKitContainer also handles all your interaction with a local database and it also handles syncing it to and from the cloud.

Multiple persistent container

What?

Usually there's a file called Persistence.swift in your project. Or your PersistenceController class is created elsewhere.

This PersistenceController instantiates a persistent container that connects to a .sqlite-database (which is defined by a .xcdatamodeld file) in your project. You reference it by name: NSPersistentContainer(name: "MyDataModel") - you need a MyDataModel.xcdatamodeld for that to work.

You could copy the whole code and instantiate a second container referencing another file.

An NSPersistentCloudKitContainer would then sync both persistent containers (read: files) to your iCloud container (read: sandbox).

Conveniently it would simply sync it to the first iCloud container in the list of iCloud containers checked in the iCloud capability.

Why?

You could want to separate topics in different databases not just different tables. For clarity or so. I.e. an app that stores your refrigerator content and your car parts. Similar database structure but different enough that two database files make sense.

If you'd want to access a private and a public part of database in an iCloud container, you'd have to use NSPersistentCloudKitContainerOptions and configurations.

Of course you could use could use configurations for that silly use case above too.

Use `NSPersistentCloudKitContainerOptions` and configurations

Say you want to connect a NSPersistentCloudKitContainer to a different iCloud container than the first in the list you marked with a checkmark.

Or you'd like to connect the public and private records in the first (or any other) iCloud container in said list.

That's what NSPersistentCloudKitContainerOptions is for.

// point to the database file
let publicDescription = NSPersistentStoreDescription(url: url!.appendingPathComponent("public.sqlite"))

// point to the container in the cloud
let publicOptions = NSPersistentCloudKitContainerOptions(containerIdentifier: "iCloud.com.nitricware.Aphrodite")

// point to the section of the container in the cloud
publicOptions.databaseScope = .public

// link the NSPersistentCloudKitContainerOptions to NSPersistentStoreDescription
publicDescription.cloudKitContainerOptions = publicOptions

// point to the configuration in your .xcdatamodeld
publicDescription.configuration = "Public"

// enable uploading already existent entries in your database
publicDescription.setOption(true as NSNumber, forKey: NSPersistentHistoryTrackingKey)

// this option enables auto refresh
publicDescription.setOption(true as NSNumber, forKey: NSPersistentStoreRemoteChangeNotificationPostOptionKey)

Further Reading: https://patmalt.medium.com/end-to-end-encryption-and-cloudkit-with-coredata-part-1-67bfbe467bc

Applying it to Core Data without cloud sync

Simply use a NSPersistentContainer and omit the lines below from the code above.

let publicOptions = NSPersistentCloudKitContainerOptions(containerIdentifier: "iCloud.com.nitricware.Aphrodite")
publicOptions.databaseScope = .public

Is there more to it?

Yes. Loads. It's a highly complex topic. I don't understand all of it yet.

Adding CarPlay to a SwiftUI Life Cycle App

Kurt Frey — Fri, 10 Sep 2021 09:56:31 +0000

This is a crosspost from nitricware.com

Apple makes it really easy for any developer with a Mac to create basic iOS apps. However, more complex topics sometimes require the developer to do lots of research. This is a blog post about adding a CarPlay Delegate to a SwiftUI Life Cycle App.

Currently, apps for iOS can either have the AppDelegate Life Cycle or the SwiftUI Life Cycle. While the latter poses many restrictions upon the developer, working with it is very smooth for the most part and - as you will soon see - very versatile.

Info.plist

Searching for tutorials about adding a CarPlay Delegate to an app leads to many results for AppDelegate based apps. A simple addition to Info.plist allows adding CarPlay to your SwiftUI life cycle app.

<key>UIApplicationSceneManifest</key>
    <dict>
        <key>UIApplicationSupportsMultipleScenes</key>
        <true/>
        <key>UISceneConfigurations</key>
        <dict>
            <key>CPTemplateApplicationSceneSessionRoleApplication</key>
            <array>
                <dict>
                    <key>UISceneDelegateClassName</key>
                    <string>YourAppName.CarPlaySceneDelegateName</string>
                </dict>
            </array>
        </dict>
    </dict>

By pointing to YourAppName.CarPlaySceneDelegateName, CarPlay knows what to do.

CarPlaySceneDelegate

Of course, you actually need a class called CarPlaySceneDelegateName. It must look like this:

protocol CarPlaySceneDelegateName: UIResponder, CPTemplateApplicationSceneDelegate {
    var interfaceController: CPInterfaceController? { get set }
    func templateApplicationScene(_ templateApplicationScene: CPTemplateApplicationScene, didConnect interfaceController: CPInterfaceController) -> Void
    func templateApplicationScene(_ templateApplicationScene: CPTemplateApplicationScene, didDisconnect interfaceController: CPInterfaceController) -> Void
}

Help me clarify things: Developing for the Oculus Go with Unity on Windows

Kurt Frey — Tue, 03 Mar 2020 18:11:53 +0000

I wanted to make a simple VR app for my Oculus Go and had to setup my environment beforehand. This tutorial tries to simplify the mentioned reference tutorial.

⁉️ Some sections of this tutorial are not exactly clear to me because I had to try things out. They are marked with this symbol: ⁉️. Please, help me improve those sections with comments.

Prerequisites

You own an Oculus Go
You own a Windows PC
Unity installed (In this case: 2019.3.3f1)
Chocolatey installed

Installations

Chocolatey installations

choco install -y adb android-sdk

Manual installations

Android SDK

When I first followed the reference tutorial, this step was not necessary to deploy to the Oculus Go. Since the reference tutorial considers it crucial, I will include those two steps, because nothing broke once I did it.

⁉️ I‘m not sure if performing the following steps makes choco install adb obsolete.

Run C:\Android\android-sdk\tools\bin\sdkmanager.bat platform-tools
Run C:\Android\android-sdk\tools\bin\sdkmanager.bat "extras;google;usb_driver"

Oculus drivers

Browse [https://developer.oculus.com/downloads/package/oculus-adb-drivers/] and download the ZIP
unzip
goto usb_driver
Right-click on android_winusb.inf > Install

Plug in your Oculus Go

Since the "allow file access" dialog did not appear once the developer account was enabled, I left it diasabled until the last step.

Plug in your Oculus Go
Allow file access on the Oculus Go
Enable developer mode via the Oculus app
Run add devices
Allow access on the Oculus Go

Setting up Unity

When installing Unity via the Hub, make sure to also install the Android tools. If it didn't work - and in my case it didn't - download via the link in File > Build Settings and install them.

Create a new 3D Project
In Edit > Preferences > External Tools disable built-in JDK and built-in Android SDK ⁉️
Click browse next to JDK and Android SDK and either search for your JDK and Android SDK or accept the path Unity found (recommende if Unity actually found something) ⁉️
Go To File > Build Settings
Click on Android and "Switch Platform" if necessary
Go To Edit > Project Settings > Player
Enter your Company Name, scroll to XR Settings and activate "Virtual Reality Support"
Add Oculus via the plus symbol to the right under "Virtual Reality Support"

Building

Go to File > Build Settings
Click Build and Run
Enjoy the VR app

And now?

Use the Oculus Utilities from the asset store and implement all it‘s features.
Make a 360 degree image the skybox like here: [https://www.youtube.com/watch?v=LXUoQ7VnLDc]
Make a Raycast like here: [https://www.youtube.com/watch?v=_yf5vzZ2sYE]

Links

Reference Tutorial

Developing for the Oculus Go with Unity on Mac

Kurt Frey — Tue, 03 Mar 2020 18:07:22 +0000

I wanted to make a simple VR app for my Oculus Go and had to setup my environment beforehand. This tutorial tries to translate reference tutorial to Mac.

Prerequisites

You own an Oculus Go
You own a Mac
Unity installed (In this case: 2019.3.3f1)
Homebrew installed

Installations

Homebrew installations

brew cask install android-platform-tools

Plug in your Oculus Go

Since the "allow file access" dialog did not appear once the developer account was enabled, I left it disabled until later.

Plug in your Oculus Go
Allow file access on the Oculus Go
Enable developer mode via the Oculus app
Run add devices on the Mac
Allow access on the Oculus Go

Setting up Unity

When installing Unity via the Hub, make sure to also install the Android tools and Open JDK.

Create a new 3D Project
In Edit > Preferences > External Tools make sure to use the built-in SDK and JDK.
Go To File > Build Settings
Click on Android and "Switch Platform" if necessary
Go To Edit > Project Settings > Player
Enter your Company, scroll to XR Settings and activate "Virtual Reality Support"
Add Oculus via the plus symbol to the right under "Virtual Reality Support"
Still in Edit > Project Settings > Player go to Other Settings and find Graphic APIs.
Remove Vulkan

Building

Go to File > Build Settings
Click Build and Run
Enjoy the VR app

And now?

Use the Oculus Utilities from the asset store
Make a 360 degree image the skybox like here: [https://www.youtube.com/watch?v=LXUoQ7VnLDc]
Make a Raycast like here: [https://www.youtube.com/watch?v=_yf5vzZ2sYE]

Links

Reference Tutorial

My first Steps in Wordpress Theme Development

Kurt Frey — Sun, 05 Jan 2020 13:33:38 +0000

Disclaimer: This is a cross-post from my dev-blog at nitricware.com.

For my new project "Geriatrie2Go.eu" - a blog about health care in geriatrics - I tried to find the perfect Wordpress theme. However, I couldn't find one that satisfied my needs. So I built one myself using Docker.

For easy development without the hassle of either installing a wordpress blog locally or shoveling my theme files after every change onto a server, I decided to use Docker. Luckily, someone created a very neat blogpost that guides you thru this process.

Creating a full fledged WordPress theme which supports all of the CMS' features can be quite exhaustive. However, WordPress is built in a way, that makes most of the work optional. For example: Once you created an index.php page you're somewhat done. Except, of course, you want page templates to look different, or single post templates or search results or...

There are great resources on how to build a WordPress theme out there. Especially the ones from the creators of WordPress;

Another topic that can make creating WordPress themes challenging for a novice like me are modern web features and the devices out there. A theme should be responsive. The simpler your theme, the simpler it is to make it responsive. I even managed to include support for dark mode.

At the end of the day, I managed to release v0.1 of wp-latex-theme, a very simple wordpress that resembles the LaTeX layout. It can be found over at Github. Please help me improve it (i.e. by adding support for comments or other post types or by localizing it). Also check out the project I made the theme for.

Adding Spotify's missing features and learning about JS, (S)CSS, PHP, APIs, Skeuomorphic Design and Documentation

Kurt Frey — Sat, 23 Jun 2018 08:56:27 +0000

This is the TL;DR section of a much - much!! - longer article over on my dev-blog. Feel free to visit the original article.

When suddenly songs in my Spotify playlists were not available anymore but an alternative version (remastered album, best-of album) could still be found, I had to add a missing feature to Spotify.

My software would find "unavailable" tracks and search for alternatives. The user could then add one of the search results to a "revived" playlist.

In the process of writing the software, I learned a lot about writing software in a very general term but also about language-specific topics, benefits of IDEs and how to design user interfaces.

I added a huge amount of comments to my code, documenting how things are done and what the code does. This does not only help myself when I review the code later on but also contributors who want to improve my software.
Knowing how paralyzing it can be when there are no responses to your questions confirmed me in my thinking that communication with other developers is a crucial tool to make your software accessible to more users.
During the process of making the application I learned about new aspects of languages familiar to me. Those aspects included type hinting in PHP, adding event listeners and dispatching events in JavaScript.
Writing JavaScript code without frameworks proved to be simple. Of course frameworks like jQuery simplify some tasks but is it worth all the required bandwidth?
Type hinting is a great tool to improve the readability of code.
Sass enables a developer to easily prototype the design of a software because of variables.
Skeuomorphic design is harder (but in my opinion more beautiful when done right) and requires you to think about your design more.
Release early or you might not release at all.

How I learned the most about using XML with PHP

Kurt Frey — Sat, 13 Jan 2018 08:50:32 +0000

Disclaimer: The software in question that used this solition was only used by two people - one of which was me. Only one of those two had write access - also me. This solution never was a business solution and was never used in production.

Quite some time ago, I was writing some PHP software for the web that would need to use a database. I wanted to design the software as portable as possible so that it wouldn't be too much hassle to migrate to another provider. MySQL was too big for what I wanted and while SQLite is powerful itself, I figured it would better suit my needs.

Sometimes when writing software, you run into a problem. Usually, there are multiple ways to solve it. My problem was, that I could not use SQLite in my PHP application, since my hosting provider did not allow me to install it and wouldn’t install it themselves.

Solution 1 would be to switch to another hosting provider which supports SQLite and run the program there. Solution 2 would be to search for another database system which does not require any installation at all. And solution 3 was what I chose to do: Write my own database solution.

While this has some very clear disadvantages like costing time, it has two main advantages. Firstly, you can control how the system behaves since you write it from scratch. Secondly, you gain a lot of experience by writing something you have never written before.

And that's how NWDatabase, a database system that comes with a PHP library and creates files with an XML syntax, was born. A software created while learning about XML, classes and much more. Surely not the best idea for production but not all that terrible for learning.

P.S.: This post was slightly altered after the first 24h, reacting on some comments.

Forem: Kurt Frey

Writing and Running Swift Code without Xcode on Mac and Windows

macOS

Windows

Linux

Target Platform

Remarks

Swift Versions on macOS

VS Code Sync

Transition from App Delegate to SwiftUI life cycle

Adding Sexual Activity to Apple Health via HealthKit

Prerequisites

Sample vs. Object

HealthConnector

Request authorization

Save a sample

Delete an object

Modify a sample

Wrapping my head around CoreData and CloudKit

Prepare your app for CoreData in iCloud

What is an iCloud container?

What is a NSPersistentContainer

What is an NSPersistentCloudKitContainer

Multiple persistent container

What?

Why?

Use NSPersistentCloudKitContainerOptions and configurations

Applying it to Core Data without cloud sync

Is there more to it?

Adding CarPlay to a SwiftUI Life Cycle App

Info.plist

CarPlaySceneDelegate

Help me clarify things: Developing for the Oculus Go with Unity on Windows

Prerequisites

Installations

Chocolatey installations

Manual installations

Android SDK

Oculus drivers

Plug in your Oculus Go

Setting up Unity

Building

And now?

Links

Developing for the Oculus Go with Unity on Mac

Prerequisites

Installations

Homebrew installations

Plug in your Oculus Go

Setting up Unity

Building

And now?

Links

My first Steps in Wordpress Theme Development

Adding Spotify's missing features and learning about JS, (S)CSS, PHP, APIs, Skeuomorphic Design and Documentation

How I learned the most about using XML with PHP

`HealthConnector`

What is a `NSPersistentContainer`

What is an `NSPersistentCloudKitContainer`

Use `NSPersistentCloudKitContainerOptions` and configurations