Creating A Web App From Scratch - Part 1 Of 8: Basic Idea And Design
At the tip of the week, we'll unleash the exact working application for you personally. What we'll create is usually a "list app". The idea concentrating on simplicity and usefulness. Sign up for your free account, and find started creating a list within a few seconds. Even the PHP dabblers on the market probably could throw such as this together promptly, right, Well the truth is, no, it isn't that easy. First of all, it must work and it must work well.
That means good tailgate end code that does how it's supposed to try and do and well. That means a great UI that's intuitive, helpful, and pleasurable make use of. It means keeping the app secure and users data private. None these things is trivial. Through this entire 8-part series, we can create an app that hopefully does these things virtually.
This "list app" will be called Colored Lists. As you finish things, you cross them off. Things on the list could be of different relative importance likewise. This makes paper lists potentially messy and inefficient. With a list with a computer, we are able to make crossing off items merely a click and you can make rearranging them a point of drag and drop.
For handling relative importance, we are able to use colorization, that could also be used for items like grouping. Computers plus the web undoubtedly are a perfect area for lists. No need to get fancy straight away. Looks like a listing to me. Each list item can be a long rectangle since the big idea here is usually to colorize each list item, so putting them within a colored box is smart.
There are a handful of interactive elements left and right of each and every list item. Those will likely be for accomplishing principle things we intend individuals be able to accomplish with their colored list. Let's take a close look. We don't necessarily strive to be talking about specific technologies at this stage, but we should be considering how the UI will operate, so we are able to make choices about technology which could accommodate our UI desires. All this stuff basically adds up to some whole bunch of AJAX.
We shouldn't load special screens to complete relatively trivial tasks like deleting an inventory item. That stuff should happen seamlessly, smoothly sufficient reason for proper feedback in reaction to clicks without page refreshes. In a sense, we're creating a one-page app, in which the majority of interaction using this type of app happens over a single page.
This is unquestionably by design, rather than trying to comply with any particular fad. Lists are quick and easy, that's why they are useful. If this app is complicated, it's usefulness is diminished and nobody make use of it. Just a little bit of quick brainstorming of the theory so far, you can come up with several "screens", or states the approval can be in. Yep, even emails should be thought about a part in the "screens", as they certainly are a vital part with the process and interaction through an app.
People love "features". Things that your app has that other apps do not have, or that yours does better. This is just the maximum amount of for marketing as it's for your actual product. All the fancy AJAX this app will have is unquestionably a feature, but that stuff currently is getting a lot more expected rather than a characteristic. The one feature that any of us will focus on using this app is "public sharing". Each list should have a unique URL which could be publicly shared. A visitor visiting this URL could see the list in their exact current state, however, not interact with becoming far as editing/adding/deleting.
0 Response to "Creating A Web App From Scratch - Part 1 Of 8: Basic Idea And Design"
Post a Comment