Tutorial 32: Core Data Basics - Storing Structured Data Locally 🚀

Featuring: The Legendary Fart Button App 💨

Welcome, brave coder! 🧙‍♂️✨ Today we're going to embark on an epic quest: learning Core Data — Apple's magical framework for storing structured data locally on iOS devices.

And yes, we're doing it with the world-changing Fart Button App. Because learning is better with farts. 💥

📚 What You'll Learn

What is Core Data?
Setting up Core Data in a project
Creating a simple Fart entity
Saving, fetching, and deleting data
Building a simple UI to interact with it

🤔 What Is Core Data?

Core Data is Apple's solution for managing an object graph — basically, storing and retrieving your app's data 🧠.

Think of it like:

User taps a button ➡️ Save a fart to the database 💨
User opens the app again ➡️ Fart history still there 📜

Without Core Data, your app would forget every beautiful fart pressed. 😢

🛠 Setting Up Core Data

Create a new Xcode project.
- Template: App
- Make sure you check "Use Core Data" ✅
Xcode auto-generates some Core Data boilerplate!
- Persistence.swift
- Model.xcdatamodeld

This is where the magic happens! 🪄

💨 Creating the Fart Entity

In Model.xcdatamodeld:

Click the + ➡️ Add Entity ➡️ Name it Fart.
Add an attribute:
- Name: soundName
- Type: String
Add another attribute (optional):
- Name: timestamp
- Type: Date

Now you have a database table ready to store farts. Historic. 🎺

🖥 Let's Build the Fart Button UI

import SwiftUI
import CoreData

struct ContentView: View {
    @Environment(\.managedObjectContext) private var viewContext
    @FetchRequest(
        sortDescriptors: [NSSortDescriptor(keyPath: \Fart.timestamp, ascending: true)],
        animation: .default)
    private var farts: FetchedResults<Fart>

    var body: some View {
        VStack(spacing: 20) {
            Button(action: addFart) {
                Text("💨 Fart Button 💨")
                    .font(.largeTitle)
                    .padding()
                    .background(Color.green)
                    .cornerRadius(12)
                    .foregroundColor(.white)
            }

            List {
                ForEach(farts) { fart in
                    Text(fart.soundName ?? "Unknown Fart")
                }
                .onDelete(perform: deleteFarts)
            }
        }
        .padding()
    }

    private func addFart() {
        withAnimation {
            let newFart = Fart(context: viewContext)
            newFart.soundName = "ClassicFart.mp3"
            newFart.timestamp = Date()

            do {
                try viewContext.save()
            } catch {
                print("😱 Failed to save fart: \(error.localizedDescription)")
            }
        }
    }

    private func deleteFarts(offsets: IndexSet) {
        withAnimation {
            offsets.map { farts[$0] }.forEach(viewContext.delete)

            do {
                try viewContext.save()
            } catch {
                print("😱 Failed to delete fart: \(error.localizedDescription)")
            }
        }
    }
}

Boom. You now have a functional fart database. 🎉

🧠 How It All Works

@Environment(\.managedObjectContext) gives access to Core Data's magical save powers.
@FetchRequest automatically listens to changes and updates the UI.
addFart() creates a new Fart entity and saves it.
deleteFarts() removes farts from history. (Pour one out. 🍻)

🧹 Pro Tips for Core Data

Always save after creating, updating, or deleting.
Use @FetchRequest smartly to drive your UI updates automatically.
Think about relationships (e.g., maybe a Fart Category later...💭).
Don't forget to handle errors gracefully.

🎯 Final Thoughts

You just built a Core Data powered app. And not just any app — a Fart Button that saves history for future generations to admire. 🏆

Next steps:

Add custom fart sounds
Add categories ("Loud", "Silent", "Squeaky") 🧩
Build a Leaderboard ("Most Farts in a Day") 🥇

The possibilities are endless... and endlessly hilarious.

DEV Community