Design phase

The design phase defines for a large part if a project will be successful.

If the design has flaws, the implementation will have flaws.
If the design is not clear, the customer’s vision will almost always be different than yours.
If the design is not complete, the customer will argue that the missing parts must be part of the solution. Delivering an incomplete product could not have been your goal, is it?

The design phase is the most important part of a project. Once everything is clear, documented and agreed, it only has to be implemented.

By saying that it “only has to be implemented”, I on purpose minify the importance of the implementation phase.

If you have a good design, you only have to write it out in code. The design will be the guide how to structure your code, classes, database tables, and folders.

I am used to writing my designs in Microsoft Word. It may not be the best tool, but with some macro’s it gets the job done.

The design can be split up in the following parts:

Interview with the customer
Write design with wireframes
Send a wireframe version of the design to the customer
Adjust the design with the customer’s feedback
Send the design to a screen designer
Replace the wireframes with the designed screens
Send the definitive version for approval to the customer
When the customer agrees, let’s start coding!

Design phase

Comments

Flutter for Line Of Business Apps

Development tools and target device

More from this blog

Anatomy of a Flutter upgrade.

Software maintenance

Consumer apps versus workforce apps

Navigator onPopPage versus onDidRemovePage, Part 2

Navigator onPopPage versus onDidRemovePage

Command Palette

Comments

Flutter for Line Of Business Apps

Development tools and target device

More from this blog