I wanted to share a checklist I've put together for redesigning an existing app for iOS7. Please feel free to suggest additions

October 10th, 2013

Hello folks,

With the introduction of iOS7, we started getting more app redesign requests here at Fake Crow. In order to help internal design teams and stake holders with design and product decisions we put together a checklist.

http://fakecrow.com/checklist-ios7-app-redesign/

I would love to hear your thoughts. I hope it helps.

Owen Rubel Creator of API Chaining, IO State, API I/O Abstraction and modern API Automation

October 10th, 2013

You know this entire list is something that web developers developing for responsive sites already do. Whats the big deal? Why not just develop a responsive website and then you don't have to worry about Android, IOS, WinBloze, or anything.

Alper Cakir

October 10th, 2013

@Benjamin Young, I haven't tried that one before, I'll check it out. Thank you

@Owen Rubel, Native vs Web apps is a big discussion on its own. There are lots of pros and cons and we try to make that decision depending on the specific case.

Benjamin Young

October 10th, 2013

Use Paintcode to turn SVG and vector based graphics directly into Core Graphics code. Save's application size and solves the whole @2x / 2x issue.

Alper Cakir

October 10th, 2013

Todd, thank you very much for the input, all valid points.

I've started this article as a checklist, mostly in order to provide a starting point for the conversations between designers and stakeholders. This is an article in the making (aka the MVP) and, with the help of feedback like yours, we want to make it as useful as possible.

Next, we hope to expand on the items we've mentioned (on individual posts) and provide more examples (as iOS 7 is so new, most of our work is still in progress and confidential).

Meanwhile I've added some examples and resources on the current link. Thanks again!

Todd Ellermann Experienced I.T. Leader, CTO, and Creative Entrepreneur

October 10th, 2013

Alper, The list is not really all that interesting unless you provide sample screens/data/ et al to illustrate what you are communicating. For example it would be hugely educational to show what a "sprite/slice sheet" was rather than assuming everyone in the world knows what it is and what a professionally done one looks like. A "spec sheet" is another example. This sentence is useless, and has some grammar problems, without a link to the resource it refers to. "Make sure your new design meets Apple’s all requirements." In the end, I was very excited to read it, and walked away disappointed. If you really want to draw some attention from it, take the time to make it a really useful document. At least link to examples if you aren't going to create your own. my $.02