Blog
If you have built a web app in the past few years, you've probably had to deal with touch events. In many cases this was limited to handling tap and removing that pesky 300ms delay. However with touch devices becoming more powerful, we now have to implement more complex gestures— gestures that work for both mouse and touch.
Functional Programming (FP) is awesome. Some of its key ideas inspired a lot of the JS practices and tools we use here at Rangle, especially React and Redux.
This blog post is the second of an in-depth, two-part series on Rangle's project design discovery process. If you missed part one, you can find it here: Project Discovery in a Lean Agile World: Introducing the Clarity Canvas.
We don’t often think of facilitation as a core skill for product designers, but there are many reasons why we should. One is that a lot of the design discovery that we do is like detective work. To design great products, you need to tease out and gather information from a wide variety of people, starting with the stakeholders on your project.
Components are an awesome tool for building interfaces. They allow you to break down the UI into distinct reusable elements. These can then be composed to build complex applications in a more sustainable way.
If you’re building web or mobile apps for an enterprise, it’s beneficial to release the minimum viable product (MVP) into the hands of your customers as quickly as possible. However, that’s easier said than done, with so many dependencies and stakeholders involved, and so many dollars at risk. As a business or technology leader, product owner, or software architect, you might fear the consequences of working with an MVP app development approach your company is unfamiliar with, or you may have heard about costly mistakes for those who dared to try. However, there is a way to avoid all that pain and instead use a highly effective MVP process.
This is the first of an in-depth, two-part series on Rangle's project design discovery process.
**This post currently reflects an earlier version of Angular, and may not be up to date or reflect the current release.** Creating components has been a topic of interest because with each release candidate version of Angular 2, it seemed like the way to do so had changed.