Mazy Dar, CEO at OpenFin, tells WatersTechnology that the API will allow central architecture teams building their own platforms to define the behavior, look, and feel of the platform, while individual development teams can easily drop applications into that environment. “So even though the apps are built by different teams, you have a nice common experience, and a common look and feel across all the applications,” he says.
He explains that application development teams are not in the business of determining how the window is going to look, what buttons go into the title bar, or what happens when users click a specific button.
“They don’t have to worry about that. They just need to worry about their specific application and know that it’s going to work nicely with everything else that’s being built for that platform,” Dar says. Typically, firms would have a central architecture team responsible for the base platform, designing the look and the feel of the platform. Then there would be various teams developing apps.
Typically, firms would have a central architecture team responsible for the base platform, designing the look and the feel of the platform. Then there would be various teams developing apps.
“But we don’t want every team to come up with their very own design, like, ‘What does the window look like?’, ‘How does it behave?’ We also want the end-user using multiple applications for all those to work together to interoperate, but also to be able to drop multiple windows into a tabbed interface, and create a common layout. And so, if every one of those teams build their own applications, you can’t really do that, and this is why we started working on Platform API,” he says.
Platform API provides default functionalities such as snapping windows together, and the ability to create a tabbed interface to conserve screen real estate. These are features and functionalities that customers have in the past built themselves on top of OpenFin.
To read the full article, click here.