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

Build the Food Review Tutorial #16

Open
1 of 8 tasks
sohilpandya opened this issue Nov 30, 2016 · 3 comments
Open
1 of 8 tasks

Build the Food Review Tutorial #16

sohilpandya opened this issue Nov 30, 2016 · 3 comments

Comments

@sohilpandya
Copy link
Member

sohilpandya commented Nov 30, 2016

I've been following the tutorial found in #14 and the idea is to create an up to date guide to building a Food Tracking app, which works with Swift 3.1

The tutorial will be split in to the following sections

  • Basic UI
  • Connect UI to Code
  • Implement Images
  • Implement Custom View Item
  • Create a Basic Data Model
  • Implement a Table View
  • Implement Navigation
  • Persist Data
@sohilpandya
Copy link
Member Author

I'll be planning to continue this for the morning and will update with my progress in the afternoon.

@sohilpandya
Copy link
Member Author

Hey @nelsonic & @iteles, I've been working on this writing up the tutorial section for this and having only reached the 2nd point, I'd like to propose something (pivot 😟)

The tutorial that Apple has created is pretty detailed, I am pretty much covering the same information that is provided in the tutorial with the exception that my codebase is updated so that it works with Swift 3.0 and upwards.

So instead of me covering it in a tutorial, I'd like to propose to do it in a screencast, where I take the user through explaining what has been achieved at the end of each section and link them to updated version of the code.

What are your thoughts on this?

@nelsonic
Copy link
Member

nelsonic commented Dec 8, 2016

Screencast is a great (better) idea.
We should still have the highlights in text if possible.
But video is definitely the way forward.

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

No branches or pull requests

2 participants