August 25, 2021
Technology | software development | thought leadership
Welcome to Create Impact, a new series from Aviture focused on the topics that inspire our engineers to innovate. In each article, an Aviture team member will take you on a deep-dive into a subject they’re passionate about, showing you the thinking behind cutting-edge engineering advances, the latest UX trends, development theories, and other unique topics that enable Aviturians to embrace the Art of the Possible for our clients.
Share
April 19, 2018
React | Redux | Technology | UX | forms
Let’s face it, forms can be extremely complicated. There are all sorts of issues you run into with forms to provide a nice user experience. That’s why it’s really handy to have a library to help you out. If using React/Redux, Redux Forms is a great library to help you manage that form state in your Store. Having Redux Forms work with the store also opens up the possibility to customize behavior via your own reducers. This will let you take advantage of all the built-in functionality of the library but also handle your potentially complicating scenarios. I’m going to show you how to leverage this concept to build a specialized form that reflects a requirement we had for a project, a derived but editable field.
Share
March 28, 2017
Aviture | Clean Coder | Culture
From the trenches, Our experiences with Style Guide Driven Development Style Guide Driven Development (SGDD) is a technique of developing your UI components in a living “Style Guide.” There is no one set definition but the basic idea is that you develop a separate page or pages outside your application that use the same CSS and HTML that your application uses. There is an excellent introduction to SGDD and its benefits at Smashing Magazine and we encourage you to check it out! This post will be about our experiences working with this technique, which suggest that on a green-field project, it is extremely difficult to know enough about your application to fully embrace SGDD out of the gate. We found that waiting for the UI patterns to emerge from your application and then creating a style guide was a better approach. Key to this recommendation is to develop and build all your UI components (style guide or not) with discipline, using known best practices.
Share
