Who should use Rivet?
If your project is an internal-facing web application, an enterprise system requiring CAS authentication, or a task-focused application separate from your organization’s website, Rivet may be right for you.See if Rivet is right for you
Q1: Rivet 1.0 release
We have added a notifications center that we will be using to make announcements about new features and updates to Rivet.
Inline validation style
We have totally redesigned inline form validation styles and created lots of great documentation to help implement them.
This quarter we have added a significant amount of new components and features including: Tabs, Dropdowns, Input groups, and Segmented buttons.
Q2: Expansion and QA
We will develop a model for extending Rivet (i.e., through plugins and widgets) so your software can have the same look and feel, no matter where it is delivered.
We want to build on our design principles (be clear, flexible, and productive) with a design philosophy. This will turn the focus towards a comprehensive view of software, and it will give insight into the why and how of UX.
A lot of designers and developers use icons in their software, but it is tough to keep them consistent. We will explore the possibility of an official IU icon set.
We want to provide guidance for how you can (or should) use Rivet. We will create example patterns, templates, and use cases to help inform your decisions.
Q3: Adoption and training
In Q3, we’ll be focusing on adding new components and design patterns to Rivet. We’ve compiled a list of the most-requested UI components and prioritized them in this project so you can follow along.
As Rivet becomes more mature, we’ll focus less on adding new components and features and spend more time creating Rivet user guides. This quarter, we’ll be working on more documentation about good design practices and how they relate to Rivet.
Technical debt and production sprint
As with any large project, technical debt and minor issues start to build up. We’re taking some time in Q3 to slow down and fix some lingering inconsistencies and irregularities in the Rivet codebase. This will give us a solid foundation on which we can continue growing.
Q4: Support and strategies
We will create a support model (tier 1, tier 2, escalation, etc.) so that the support center can handle basic questions and escalate more complex ones to the Rivet Team.
It is helpful to hear how others use Rivet to solve problems. It is even better to see those solutions in action. We will set up a gallery of published applications using Rivet to inspire and inform.
Applications sold by IU may need to use different branding, styles, or packages. We’ll create “white label” options that make it easier for application owners to substitute Rivet styles with their own.
We need to make sure that Rivet stays relevant, updated, and useful for years into the future, so we will explore sustainable strategies and plans to ensure longevity.