Post a first pass at designs. Show all the screens you need to tell the story of your app—you don't need to design social media login screens or show your settings if they're not central to the app—show what's important to the user.
In general: Be able to explain what your app is in one short sentence. Critics should understand what you're trying to accomplish right away.
Showing posts with label Joana Kelly. Show all posts
Showing posts with label Joana Kelly. Show all posts
4/10/14
4/3/14
Assignment for April 10
Next week iterate on your wireframe and make a prototype. Looks like folks like Flinto, so feel free to use that or POP, or go for paper if that's more your style. You'll present the prototype to other groups in class.
Here's the presentation from today's lecture on Agile and Scrum.
Here's the presentation from today's lecture on Agile and Scrum.
3/20/14
App Marketing
https://www.icloud.com/iw/#keynote/BALQX0kfjELAl-PmUEeBK44PH_81cwB5GRCF/Presentation
iOS marketing guidelines
Android marketing guidelines
(This a year old, but it's a pretty thorough look at app marketing if you want to look into it. A quick Google search will bring up tons of other resources—this is just one of many.)
iOS marketing guidelines
Android marketing guidelines
(This a year old, but it's a pretty thorough look at app marketing if you want to look into it. A quick Google search will bring up tons of other resources—this is just one of many.)
Assignments for April 3rd
Next week is SPRING BREAK!
Woooo!
For the following week, iterate on your concept and develop a first pass at an app map and wireframes. Post to the blog and tag accordingly.
A word on app maps:
Remember that each view should be represented in the app map, and it should be clear from the map from where the user can get to that view (hence the "map"). Your map needs to make sense!
A word on wireframes:
Do NOT start designing your app yet—it's distracting at this point in the process. Keep it simple. Pencil and paper is completely fine.
------//------
EXTRA CREDIT ASSIGNMENT
Based on the critics' feedback you received on your midterm presentation, iterate on three views from your Project 1 app. You can create three new views or make edits and changes to existing views—whatever makes sense in your case. The idea is to show how you would continue to improve and evolve the concept, the flow, and/or the design.
Do not do more than three views.
Do not do fewer than three views.
ALSO. Write a short paragraph about your thinking behind the changes you've made, why you made those particular decisions, and what other changes you would make (if applicable) in the rest of your app.
Post to the blog before next class.
Woooo!
For the following week, iterate on your concept and develop a first pass at an app map and wireframes. Post to the blog and tag accordingly.
A word on app maps:
Remember that each view should be represented in the app map, and it should be clear from the map from where the user can get to that view (hence the "map"). Your map needs to make sense!
A word on wireframes:
Do NOT start designing your app yet—it's distracting at this point in the process. Keep it simple. Pencil and paper is completely fine.
------//------
EXTRA CREDIT ASSIGNMENT
Based on the critics' feedback you received on your midterm presentation, iterate on three views from your Project 1 app. You can create three new views or make edits and changes to existing views—whatever makes sense in your case. The idea is to show how you would continue to improve and evolve the concept, the flow, and/or the design.
Do not do more than three views.
Do not do fewer than three views.
ALSO. Write a short paragraph about your thinking behind the changes you've made, why you made those particular decisions, and what other changes you would make (if applicable) in the rest of your app.
Post to the blog before next class.
3/13/14
Assignments for March 20th
New week, new project!
Project 2 is a group based project. You can make your project be about whatever you like. For next week, please post your app concept to the blog and be prepared to present it to the class for feedback.
Things to keep in mind:
*Who are your users? Be specific.
*What is the app for? Why do your users need it/want it?
*How will your app work?
You can be as fanciful or realistic as you like with your concept, but it should make sense!
Tag your post with all of your team members' names, "project2," and "concept."
If you haven't posted a ThursdayApp yet, you must do so before next week!
Project 2 is a group based project. You can make your project be about whatever you like. For next week, please post your app concept to the blog and be prepared to present it to the class for feedback.
Things to keep in mind:
*Who are your users? Be specific.
*What is the app for? Why do your users need it/want it?
*How will your app work?
You can be as fanciful or realistic as you like with your concept, but it should make sense!
Tag your post with all of your team members' names, "project2," and "concept."
If you haven't posted a ThursdayApp yet, you must do so before next week!
2/27/14
Assignments for March 6
Design time!
Based on the results of your prototyping, fix up your wireframes and start designing the views. Write out what you learned from prototyping and how it affected your designs. Please post your designs on the blog and label the post "design" and "project 1."
I know not everyone is a designer by trade, but do your best with the tools you have.
You'll present your designs next week in class. Each person will get 7 minutes to present. I'll either give you feedback on the fly or send it to you in writing.
Based on the results of your prototyping, fix up your wireframes and start designing the views. Write out what you learned from prototyping and how it affected your designs. Please post your designs on the blog and label the post "design" and "project 1."
I know not everyone is a designer by trade, but do your best with the tools you have.
You'll present your designs next week in class. Each person will get 7 minutes to present. I'll either give you feedback on the fly or send it to you in writing.
Some notes on testing with your prototypes:
1) Pay attention to what users do, not what they say.
2) Don't lead your users. Give them a task, and then watch what they do.
3) It's an observation, not a conversation. Don't totally shut down, but don't banter away either. Be a scientist!
Here are a couple of excellent articles from Nielsen about usability testing:
2/20/14
Assignments for Feb 27
1. TAG YOUR POSTS
2. Create paper or POP prototypes of your wireframes and share them on the blog.
If you make a paper one, you can just snap a photo to document it and post that.
If you use POP, you can share a link directly from the app. Tag your post with "prototype" please.
Next week you'll be using the prototypes in class to prove out your wireframes.
Here is POP's sample app.
2. Create paper or POP prototypes of your wireframes and share them on the blog.
If you make a paper one, you can just snap a photo to document it and post that.
If you use POP, you can share a link directly from the app. Tag your post with "prototype" please.
Next week you'll be using the prototypes in class to prove out your wireframes.
Here is POP's sample app.
2/13/14
Assignments for Feb 20
First things first:
For the love of all that is good—TAG YOUR POSTS. Use the Labels button to do so.
For next week:
Post a second iteration of your wireframes to the blog. I'll send you feedback via email to the 1st iteration. Document in your wireframes how you'd include accessibility features.
Some reading:
This is an excellent piece by Matt Gemmell—please read:
http://mattgemmell.com/accessibility-for-iphone-and-ipad-apps/
Information about iOS accessibility features:
https://www.apple.com/accessibility/ios/
https://www.apple.com/ios/accessibility-tips/
Information about Android accessibility features:
http://developer.android.com/guide/topics/ui/accessibility/index.html
http://developer.android.com/tools/testing/testing_accessibility.html
For the love of all that is good—TAG YOUR POSTS. Use the Labels button to do so.
For next week:
Post a second iteration of your wireframes to the blog. I'll send you feedback via email to the 1st iteration. Document in your wireframes how you'd include accessibility features.
Some reading:
This is an excellent piece by Matt Gemmell—please read:
http://mattgemmell.com/accessibility-for-iphone-and-ipad-apps/
Information about iOS accessibility features:
https://www.apple.com/accessibility/ios/
https://www.apple.com/ios/accessibility-tips/
Information about Android accessibility features:
http://developer.android.com/guide/topics/ui/accessibility/index.html
http://developer.android.com/tools/testing/testing_accessibility.html
2/7/14
Linky links
1) Facebook Paper's gestural hell
"There's no doubt that Paper is a fresh and innovative take on content
browsing. But while Paper may not ask much of us when we sign up to use
the app — it asks a lot of us when it comes to the app's default
interactions. So much so that the Paper's heaviest users might need to
start popping arthritis medication in a few years."
Download Scott Hurff's Thumb Zone template here from Dropbox (Includes a Sketch file and a JPG).
2) Leading Designers At Square, Dropbox, And Flipboard On How To Land A Dream Job: Six mistakes designers make in interviews with startups, and how to avoid them
"The most important thing a designer submits in an application is their portfolio of work," says Kerksick of Change.org. "Oftentimes these portfolios show just the result, which doesn’t tell me much. Projects that challenge me with a problem; take me through the ugly, messy process; then inspire me with their solution--those are impressive."
3) 7 Lessons Learned From Interviewing 100+ App Developers
On the web, the more features a product has, the more robust and appealing it is to many of us. On the other hand, in the fragmented mobile space, it is better to have less features and do one thing really well.
2/6/14
Assignments for Feb 13
Some housekeeping:
Assignments for next week:
1. Post your app idea. Remember, it should be related to New York in one way or another. I'll provide you with some feedback and then you can move onto your wireframe and app map.
2. Create an app map and a wireframe for your app and post it to the blog for presentation in class next week. Everyone will get 5 minutes to present, and about 3 minutes of feedback. You'll be timed, so that everyone has a chance to present!
- Tag your posts! Blogger calls them Labels for whatever reason. The Labels button sits on the right side of the screen while you're writing a post.
- Please do NOT tag your posts with NextWeeksAssignments—I'll use that to tag assignments.
- Go into settings and make sure your username is your actual name, so that I can properly identify who is posting what.
- Titles for your posts wouldn't hurt either...
Assignments for next week:
1. Post your app idea. Remember, it should be related to New York in one way or another. I'll provide you with some feedback and then you can move onto your wireframe and app map.
2. Create an app map and a wireframe for your app and post it to the blog for presentation in class next week. Everyone will get 5 minutes to present, and about 3 minutes of feedback. You'll be timed, so that everyone has a chance to present!
1/30/14
#ThursdayApps
Here are the apps we talked about today, including the apps you guys brought up in class:
Introducing Paper from Facebook on Vimeo.
Beats Music App
Dark Sky
WunWun
Mint
Sleep Cycle
The Human Body
Introducing Paper from Facebook on Vimeo.
Beats Music App
Dark Sky
WunWun
Mint
Sleep Cycle
The Human Body
Assignments for Feb 6
Welcome to Mobile Media!
For next week:
Read the iOS Human Interface Guidelines and/or the Android Design Guidelines.
Please post a photo of yourself, your name, your current favorite app, and at least three things from the iOS Human Interface Guidelines and/or the Android Design Guidelines that surprised you, confused you, or enlightened you. Tag with your name and "guidelines".
In a separate blog post, please share your group's designs for at least two screens from the App Scramble. [Only one of you from the group needs to do this.] Be ready to present your app in next week's class—five minutes to present, and five minutes for feedback for each group. Tag with "App Scramble" and the names of each person in your group.
Post a #thursdayapps if you've got one in mind! Tag with "#thursdayapps." You need to post at least two over the course of the class, one before spring break and one after.
Start thinking about Project 1 ideas. Feel free to post it early for some feedback, if you feel so inclined, and please tag with "Project1."
For next week:
Read the iOS Human Interface Guidelines and/or the Android Design Guidelines.
Please post a photo of yourself, your name, your current favorite app, and at least three things from the iOS Human Interface Guidelines and/or the Android Design Guidelines that surprised you, confused you, or enlightened you. Tag with your name and "guidelines".
In a separate blog post, please share your group's designs for at least two screens from the App Scramble. [Only one of you from the group needs to do this.] Be ready to present your app in next week's class—five minutes to present, and five minutes for feedback for each group. Tag with "App Scramble" and the names of each person in your group.
Post a #thursdayapps if you've got one in mind! Tag with "#thursdayapps." You need to post at least two over the course of the class, one before spring break and one after.
Start thinking about Project 1 ideas. Feel free to post it early for some feedback, if you feel so inclined, and please tag with "Project1."
1/14/14
Subscribe to:
Posts (Atom)