Roche and Appsilon Build on Their Collaboration to Support teal’s Continued Development

[This article was first published on pharmaverse blog, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Following the recent migration of the teal framework to pharmaverse, Roche and Appsilon are building on their existing collaboration to support its continued development. Appsilon will continue contributing developer expertise and will be recognized as a core contributor and copyright holder alongside Roche.

teal helps developers build Shiny applications for exploring clinical trial data. If you’ve worked with it, you’ll know its modular approach: combining data, filters, and analysis modules into interactive applications.

Appsilon has been working with Roche on {teal} development and has been a core contributor to the open-source library. For example, it has co-implemented the new teal design, teal.reporter, and teal.picks, changes that have improved the quality and capabilities of the framework. Formal recognition as a core contributor is a new step forward that formalizes Appsilon’s role in the project, alongside Roche and the wider community.

What Changes for Users and Contributors?

The teal framework packages are now hosted in the pharmaverse GitHub organization, as described in the earlier migration announcement. Users of existing released versions do not need to change their R code as a result of the move. For development versions installed directly from GitHub, we recommend updating package references to their new pharmaverse locations.

Appsilon will continue co-leading the maintenance and development of the teal framework alongside Roche, with input and contributions from the wider community. This continued collaboration supports the framework’s ongoing development while welcoming other companies and individual contributors to help shape its direction.

Users and contributors can continue reporting issues, proposing features, and submitting pull requests in the package repositories. Community feedback and contributions remain an important part of teal’s development.

What’s Next for teal?

Future development will focus on making teal easier to contribute to and strengthening its use in validated environments. Work includes expanding guidance for AI-assisted development across the core and module packages, alongside improvements to testing and dependency management. Roche and Appsilon will continue working with the wider community to shape priorities and guide the framework’s development.

Building on the Community’s Work

teal was created at Roche and has grown through the work of developers and users contributing code, modules, documentation, bug reports, and feedback. Appsilon has been a vital part of the teal community and is taking on a greater role in its continued development alongside Roche and other contributors.

Thank you to each author of teal: Dony Unardi, Dawid Kałędkowski, Pawel Rucki, Aleksander Chlebowski, Andre Verissimo, Kartikeya Kirar, Vedha Viyash, Marcin Kosinski, Adrian Waddell, Nikolas Burkoff, Mahmoud Hallal, Maciej Nasinski, Konrad Pagacz, Junlue Zhao, Tadeusz Lewandowski, Lluis Revilla and everyone else who has helped develop and maintain the project. We look forward to continuing to work with you and welcoming new contributors.

It’s been rewarding to see teal grow and support colleagues across the biotech and pharmaceutical community. Moving to pharmaverse opens a new chapter in that journey, and I’m excited to build on our longstanding collaboration with Appsilon through a shared commitment to open-source development. Together with the wider community, we look forward to shaping teal’s future and expanding what it can help users achieve.

— Dony Unardi, Roche (teal Product Owner and NEST Chief Engineer)

We are excited to welcome Appsilon as a partner for teal. Open source ecosystems like pharmaverse thrive when dedicated communities and forward-thinking organizations step up together as one – enabling powerful frameworks like teal to flourish and drive real impact. We hope this move to the pharmaverse org also encourages further contribution from across the industry, so this continues to prosper.

— Ross Farrugia, Roche (pharmaverse co-founder)

teal is a great example of the unique value of open-source software and the power of an active community. Having co-developed teal over the past two years, we are excited to begin this new chapter as copyright holders. We look forward to engaging even more closely with the community as teal moves to the Pharmaverse GitHub organization.

— Oriol Senan, R/Shiny developer at Appsilon, contributor to teal

If you use teal, your feedback helps shape it. Report an issue, suggest an improvement, contribute a module, or join the conversation in the Pharmaverse Slack’s #teal channel.

Explore the repository · Read the documentation · Read the contribution guide

Last updated

2026-11-03 18:52:55.526917

Details

Reuse

Citation

BibTeX citation:
@online{unardi2026,
  author = {Unardi, Dony and Veríssimo, André and Senan, Oriol},
  title = {Roche and {Appsilon} {Build} on {Their} {Collaboration} to
    {Support} Teal’s {Continued} {Development}},
  date = {2026-11-04},
  url = {https://pharmaverse.github.io/blog/posts/2026-11-04-roche-appsilon-teal/roche-appsilon-teal.html},
  langid = {en}
}
For attribution, please cite this work as:
Unardi, Dony, André Veríssimo, and Oriol Senan. 2026. “Roche and Appsilon Build on Their Collaboration to Support Teal’s Continued Development.” November 4, 2026. https://pharmaverse.github.io/blog/posts/2026-11-04-roche-appsilon-teal/roche-appsilon-teal.html.
To leave a comment for the author, please follow the link and comment on their blog: pharmaverse blog.

R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Never miss an update!
Subscribe to R-bloggers to receive
e-mails with the latest R posts.
(You will not see this message again.)

Click here to close (This popup will not appear again)