In this tutorial video we’ll get fancy with Autocomplete! We’ll look at some sweet little tricks that you can use when you’re working with small datasets. Both Local and Remote/Server side sets of data can be handled in a similar once the data is available to AngularJS.
We’ll pick this video up from the end of the AngularJS Material Design Toolbar Tips and Tricks and extend it out further to get working Tabs with external templates, and ui-router, we’ll also look at forms, and toasts.
We go behind the scenes with early designs for a Material Design Web App that I’m working on, and some insight into the types of things that designers need to consider for UX that is created for a specific audience.
I’ve been playing around with Angular Material a lot lately, and I’ve been really impressed with how easy it is to create pretty web apps, (once you get the hang of it).
There are so many cool things that I’d like to share, but I don’t know where to begin! So in this video, I’ll take you through my latest side project, and show you the types of things that are possible.
An introduction to functional design. We’ll identify a subset of requirements and create an interaction flow. We’ll then look at each step in the interaction flow with: use cases, storyboards, wireframes and business rules.
Once we’ve locked in a set of requirements, we can start designing! We’ll begin by creating a list of use cases, and storyboards (scenarios). Storyboards and wire-frames are often created in parallel, and changing one normally leads to changes in the other.
Behaviour driven tests are also a great way to make sure that the requirements aren’t forgotten about as the project progresses. There’s no better way to show progress than when you can easily show how many tests are passing at any point in time.
This approach is not too dissimilar from something that you might see in a business case. After all, the more we understand about the business drivers, the more we can reduce assumptions, and focus on the real, underlying problems.
A context diagram is a great place to start exploring. It lets us look at a problem from the outside, and peel away the layers until we get to the core. This is a great way to understand how a business interacts with the entities that live outside of it.
New customers are often referred to App-Makers by existing or previous customers (which is a great thing!). However, this can often mean that early interactions with a customer are recorded in Facebook chat, SMS messages, and emails with different members of the team.
To help lift the veil of secrecy around where software comes from, and how to actually make it work for you and your business, lets go through a step by step approach of architecting, designing, and developing a web app.
I’ve been using the MEAN stack for quite some time now (MEAN is a web app stack which consists of MongoDB, Express, Angular, Node). In the last few months, the stack, predominately the ‘A’ (Angular.js) part of the stack has gone through a process of transition. This has been a bit of an awkward time […]
GitHub: has millions of public and private repositories, with thousands more being added everyday. GitHub repositories or ‘repos’, are used as a collaborative means of source control. Github allows a granular level of change control and code management. This means that code changes can be clearly identified, issues can be addressed, and new features can be requested, all in one place.