Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Friday lab #10

Open
wants to merge 18 commits into
base: master
Choose a base branch
from
Open

Friday lab #10

wants to merge 18 commits into from

Conversation

robert-hatfield
Copy link
Owner

User Stories (MVP)

  • As a developer, I want to utilize UIKit to build out an application to gain a working knowledge of Apple's primary UI framework.
  • As an iOS developer, I want to design and implement a clean and delightful UI/UX, to improve my user's experience when using my Application.

Technical Requirements

These technical requirements are vague and fairly lightweight intentionally. This is to provide additional time to finish implementing any desired features or stretch goals into the application. Feel free to experiment and think up new features that you may think a user would like. The primary goal is submitting an application that looks, and feels, user ready. For the colors, fonts, layout, and view controller transitions, there is nothing wrong with using any of the Apple provided defaults. Apple and other companies use them often, in subtle ways, to achieve a clean, cohesive UI/UX.

  • Continue to work from the same repository.
  • Working on a non-master branch, called, friday-cleanup with regular commit history
  • Implement a color scheme to your application to highlight different features of you UI. Also, you may optionally choose to include any additional assets you would like to use to improve the appearance of your UI.
  • Find a font that is visually appealing and implement it into your application.
  • Comb through and polish the layout of your views, buttons, and labels.

I also cleaned up commented-out code & print statements used while debugging.
I'll need to adjust this to display a user-friendly name for each filter.
I made lots of little UX tweaks (alternate animation durations, adjusted logic of how & when the preview collection view may be dismissed, disabled filter button if user has not loaded an image) that should have been committed separately.
The filter actions are no longer on an action sheet, but since the assignment called for a refactor, actions when tapping on the main image view should now be more modular. With only 3 possible actions, this only saved about 2 lines of code.
Also added more marks for extensions
This keeps user-friendly names and CoreImage names together.
Appending to history after each filter is applied to the primary image. Undo / reset not yet available.
Undo button isn't operational yet; I'll set it to appear only when one or more filters have been applied.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant