This translation is incomplete. Please help translate this article from English.
Note: The Quickstart section has been updated with a new, more focused Quickstart article, which replaces all the previous Quickstart articles. We hope you'll find this more useful, and a quicker learning experience than the older set of articles.
What is the purpose of your app?
Look around your world, find an unmet need, and then address it. If you already have a list of tasks, an idea for your app and the type of user you are targeting, it's time to create a goal statement: Define your app's purpose and the most important user in one sentence. This is your main use case.
Example: A wish list creation tool for people who never do impulse shopping.
Focus on one main use case
It is possible that you cannot include all the tasks on your list in your goal statement. That is ok, because you should focus on one main use case, which is how most people will use your application. Awesome apps do one thing well.
Design Your Thoughts
There are lot of methods to design ones own idea,native work techniques like paper and pencil is an ideal method to put your ideas this later helps in furnishing them or upgrading the thoughts .But the web is expanding day by day , there are apps to keep your designs more creative like Invision and new guy in town which was funded through kickstart campaign,and Uxpin a wireframing app . Both are best for Prototyping.
How will people use your app?
By now, you've identified your main use case, target users, and key features. Your main scenario should also consider the user environment in which your app is used. For example, a young mom with her baby at daycare might use your app to note a nice stroller (potential multi-tasking, pausing and continuing the task later). A different user might plan her next laptop purchase at home, in an armchair, without interruptions.
Concentrate on a few key features
Look at your task list again. Filter your list through the goal statement. If the tasks do not align with your goal statement, exclude them in your app.
Describe each core task as a feature and then ask yourself, is this feature essential? Or is it nice-to-have but not required by the target user to complete the defined task? Be honest with yourself. If you end up with a short list of features, you are on the right track.
Remember, the best apps usually do one thing well. Apps often fail not because they have too little features, but too many.
The best way to win the users heart is by design,the best your design and working elements you have you can let the users hold on to your app ,one more thing focus on one element at a time and rest are upgraded with time.