Swift中Data Model是什么？为何需在Model文件夹单独编写而非ViewController？

Great question—let’s break this down clearly since structuring code well is such a foundational part of building maintainable iOS apps (like your Quiz app!).

What is a Data Model? #

A Data Model is essentially a blueprint for the data your app uses, plus any core logic tied to that data. In Swift, this is usually a struct or class that defines properties to hold data and methods to handle operations related to that data.

For your Quiz app, a perfect example would be a QuizQuestion model:

struct QuizQuestion {
    let questionText: String
    let options: [String]
    let correctAnswerIndex: Int
    
    // A method tied to the data: check if a user's answer is correct
    func isAnswerCorrect(_ selectedIndex: Int) -> Bool {
        return selectedIndex == correctAnswerIndex
    }
}

This model encapsulates everything about a quiz question: what the question says, the possible answers, which one’s right, and even how to verify an answer. It’s self-contained—all logic related to "what a quiz question is and does" lives here.

Why Not Put All Code in ViewController? #

ViewController files have a specific job: they act as the middleman between your app’s UI (the View) and your data/business logic (the Model). If you cram everything into ViewController, you’ll hit big problems fast—here’s why separating code into a Model folder matters:

• Readability & Maintainability: Imagine your Quiz app grows to 50 questions, plus logic for scoring, tracking progress, and shuffling questions. If all that code lives in ViewController.swift, the file could easily balloon to thousands of lines. Trying to find where to fix a UI button vs. where to adjust how scoring works becomes a nightmare. Separating models keeps code organized—you know exactly where to go for data-related changes.

• Reusability: Suppose later you want to add a results screen that shows users all the questions they got wrong. If your QuizQuestion model is already defined, you can pass those questions directly to the results screen’s ViewController without rewriting the question structure. Reusing code saves time and reduces bugs.

• Testability: It’s way easier to write unit tests for a standalone model. For example, you can test if isAnswerCorrect(_:) returns true when the right index is passed, without having to simulate tapping a button in the UI. Testing business logic separately makes your app more reliable.

• Single Responsibility Principle: This is a key software design rule—each component should have one job. ViewControllers should handle updating the UI and responding to user taps. Models should handle storing data and processing business logic. When each part sticks to its lane, your code is less likely to break when you make changes.

Wrapping Up #

Separating your data models into a dedicated Model folder isn’t just about following rules—it’s about making your code easier to work with now and scale later. For your Quiz app, this means you can tweak question logic, add new question types, or update scoring without touching the code that controls buttons, labels, or other UI elements.

内容的提问来源于stack exchange，提问作者Yuri Light