In this lab, you will create a simple shopping calculator. It will only have one screen and limited functionality, but it should help you get comfortable with Xcode, UIKit, and Swift. Please read this entire document before getting started.

Please test opening your zip file on another computer to make sure the files are included properly. TAs are not liable for broken submissions and the late penalty will apply.

Description

This lab requires you to create your own app from scratch. Although many of the implementation details are left to you, there are some helpful guidelines and code snippets to get you started in the Helpful Advice and Code Snippets section below. Many of the topics covered in this lab have been discussed in lecture as well. Additional resources are available online in the Swift documentation and UIKit documentation that Apple provides.

The goal of this lab is to create a simple shopping calculator that calculates the final price of a product based on its original price, the current discount percentage, and the local sales tax. The calculator should be easy to use. Everything should appear on the same screen, with labels and text fields that the user can edit. Whenever one of the fields is changed, the final price of the product should be updated.

Creative Portions

For each lab we will have you add features that improve the user experience and deepen your swift knowledge. These features are what we call the creative portion. This is your opportunity to add new feature(s) to your app that are interesting to you and not covered in the other requirements. Everyone is tasked with making a shopping calculator: how can you make yours truly stand out? This could involve totally changing the end behavior of your app.

If youre struggling to come up what to implement, imagine yourself as a user and think about what you would want in the app. A good creative feature is original and it enhances the user experience. Feel free to search online for implementations of advanced features, but please do not directly copy-paste some lines of code you found online. An example of a bad creative feature is one that limits user functionality, such as replacing text fields with sliders.

In order to get full credit, the creative portion should be substantial enough to merit the amount of points listed. Compare the difficulty of implementation and the utility of your added feature of your feature to the other features in the requirements section. The goal of the creative portion is to add something new and different, not just re-hash existing requirements.

When submitting your lab it is your chance to sell it to us. The more you tell us about your app the better. As a minimum please tell us three things about your creative feature(s):

1. What you implemented
2. Include usage instructions if you think your feature is vague
3. How you implemented it
4. Why you implemented it

This format will be the standard moving forward. Please make sure this information is in the email body.

Requirements

[20 points] Users can input the original price, discount percentage, and sales tax percentage for a given product. Each of these fields has a corresponding label.

[5 points] Whenever a text field is changed, the final price of the product is updated live.

[5 points] The final price is correctly calculated (and rounded).

[5 points] The app behaves appropriately given any possible input.

[5 points] The layout of the app is clean and easy to use.

[10 points] Creative portion: Add one other small feature that improves your application.

Helpful Advice and Code Snippets

It is going to be easiest to use the Storyboard for the layout of the app. Use your previous studio Xcode project for reference on how to add outlets and connections from the Storyboard to code. The built-in UIKit objects are sufficient to complete this lab a combination of UILabels and UITextFields should do the trick.

In order to update the final price of the product live, UITextFields have an Editing Changed event, which can be connected to your code via an IBAction. It is not sufficient to have the final price update only when the editing finishes the app should feel responsive even as the user is typing.

To round the final price to two decimal places, one method is to use the Strings format constructor like so:

let displayText = $(String(format: %.2f, finalPrice))

Consider what happens with various edge cases. What should be displayed when the text fields are empty, zero, negative, extremely large numbers, or not-numbers? This is up to you, but your choices should be sensible and not crash the app.

An example of a working shopping calculator. Feel free to design the layout as you see fit!