Tasks will be assigned via the Issues tab above. You will find your username beside your assigned task.
When implementing a feature, create a new branch for that particular feature. The naming standard for branch should follow a lower-cased pattern, separated words by hyphens, and followed by the task number (ex: home-screen-view-1).
Remember, a branch is simply a copy of the main codebase that you can freely manipulate without affecting the main code.
Do not make changes to the main branch. If you finish an implementation/task, make a pull request to request merging your branch with main. I will approve your pull request if I don't find any faults.
It's important that you understand the navigation mechanism we'll be using for this project. SwiftUI offers many different methods of navigation, however a combination of NavigationStack and NavigationPath suits our app best.
NavigationStack: takes in a root view and aNavigationPathobject which the stack responds to. The root view is simply the starting screen with which you'll enable navigation. When the navigation path is empty, the root view is displayed. The navigation path offers a seamless way of returning to prior screens and jumping to new ones..navigationDestination(for: ..., destination: ...): responds to a new item added to the NavigationStack's NavigationPath, if the new item matches the type specified after 'for', a jump to the destination is triggered. That destination corresponds to the last element in the path.
struct NavigationExample: View {
// An empty navigation path is initialized, we will append elements as we want to move to new screens, and pop elements whenever we want to backtrack
@State var path = NavigationPath()
var body: some View {
// The stack we wrap around our starting screen. It enables all the necessary interactions for navigation.
NavigationStack(path: $path, root: {
Button("Click to go to next number", action: {
// Adding an element to the end of the path, prompts a jump to a new screen
path.append(Int.random(in: 0...1000))
}) // Determines the destination UI upon appending an integer to the path, as indicated by 'for: Int.self'
.navigationDestination(for: Int.self, destination: { pathElement in
Button("\(pathElement). Click to go to next number", action: {
// Prompts a jump to another screen
path.append(Int.random(in: 0...1000))
})
Button("Back") {
// Prompts a return to the prior screen
path.removeLast()
}
})
})
}
}Support for photo library and camera access is yet to be provided in SwiftUI, thus we have created a reusable photo picker and camera view using the UIKit framework (SwiftUI's predecessor). The views were initialized in UIKit, however you can use them as you like in your SwiftUI code. The provided views are:
ImagePickerView(showImagePicker: image: ): accesses the photo library of the device in the form of a view, takes in a binding to a boolean indicating whether it should be displayed, and a binding to an image which it will manipulate as the user selects an image.CameraView(showCamera: image: ): accesses the camera of the device in the form of a view, takes in a binding to a boolean indicating whether it should be displayed, and a binding to an image which it will manipulate as the user takes photos.
Take the below code as an example.
struct ImageView: View {
@State var image: UIImage? = nil
@State var showPicker = false
@State var showCam = false
var body: some View {
VStack {
Button("Click to bring picker.") {
showPicker = true
}
Button("Click to enable camera.") {
showCam = true
}
if let image = image {
Image(uiImage: image)
.resizable()
.aspectRatio(contentMode: .fit)
}
}
.frame(maxWidth: .infinity, maxHeight: .infinity)
.sheet(isPresented: $showPicker, content: {
ImagePickerView(showImagePicker: $showPicker, image: $image)
})
.overlay(content: {
if showCam {
CameraView(showCamera: $showCam, image: $image)
.ignoresSafeArea()
}
})
}
}We'll be using @EnvironmentObject property wrapper in all views beside HomeView. It allows for an easier sharing of class objects among subviews and screens. Research it to gain an understanding of how it works before proceeding (how to receive it in other views, etc.).
A few bonus features to consider implementing should you finish all app features early:
- Cache user data on device using the CoreData framework or SwiftData framework.
- Implement object isolation on clothing snapshots, same feature the Photos app uses (https://developer.apple.com/videos/play/wwdc2023/10176/).
