![]() ![]() In addition, being able to test everything directly on the final product using the real hardware was an absolute game changer for us! Conclusion and Quick Tips Having a dedicated component library as a single source of truth, building UI components in isolation while still being able to communicate between them, gives me the flexibility I haven’t found anywhere else yet. ProtoPie’s advanced component features allow me to go far beyond just transitioning between more or less static screens. Throughout the years I have tested and used a wide range of tools, often resulting in frustration due to technical limitations or a lack of functionality. Prototyping has always been a crucial part of my workflow, it helps me to visualize, test and iterate ideas quickly without wasting too much time. By making use of ProtoPie’s advanced component features we could develop elements further to use or work on pieces separately and then settle them together into the final piece. To meet our deadline, we also needed the possibility to work together at the same time. ![]() It was just the perfect project to take full use out of ProtoPie’s capabilities in terms of real-time data connection, multiple hardware devices and screens. Having worked with ProtoPie before and thus knowing what the software can do brought us directly to the conclusion, that this is the best tool to get the job done. We wanted to create a highly sophisticated prototype, which gives users a good impression of our ideas, allows us to iterate quickly and come up with a solution in an extremely short timeframe. With an emphasis on hardware integration and personalisation, we knew we needed an advanced design software, one that went far beyond the limits of static screens. Also, they already set up everything to have full control over every hardware part in the car! Having all those capabilities at the palm of their hand they needed a visual representation to convince stakeholders. Envisioning a new car HMI from scratch seemed like one of the coolest projects I could have imagined. At the time we joined in on the project, Elexir had already established their software architecture. I got hooked by their idea right off the bat. By using an open-source software approach they are enabling everybody to contribute to its system and giving customers the ability to replace and add hardware elements and benefit from further software improvements. They achieved this by developing a completely new underlying software architecture. They built a highly customizable and extendable shared car, trying to attain the same experience as of owned, personalised cars. Current Component - Solely the current component, not any child components if there are any.Earlier this year the start-up Elexir reached out to us with their unique vision of creating a more sustainable car.Current Scene - The scene where the component is used.Child Component - Any child components in the current component you are in.Parent - Parent component or scene if there’s no parent component.You can choose between these channels under Inside Pie now: ![]() We made some changes following the introduction of nested components. As components are isolated from scenes, the Send response and Receive triggers were initially used to create interactions between a component and objects outside of a component. If you are familiar with using components in ProtoPie, then you must be familiar with the Send response and Receive triggers as well. This is what you’re most probably used to from components in the design tools you already use. ![]() The parent component can override the child component, and so on. You can override nested components at any level of the component hierarchy. Example prototype using nested components. ![]()
0 Comments
Leave a Reply. |