skydoves/balloon

:balloon: Modernized and sophisticated tooltips, fully customizable with an arrow and animations for Compose and Kotlin Multiplatform.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 47 minutes ago
Added to GitGenius on September 17th, 2026
Created on July 14th, 2019
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 309
Total Stargazers: 4,008 (+0)
Total Subscribers: 25 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.2 days
Mean response time: 69.8 days
90th percentile: 300.3 days
Tracked items: 61

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 1,065 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Release Next (22)
  • compose (8)
  • Released (3)
  • enhancement (2)

Detailed Description

Balloon is a tooltip library for Compose and Kotlin Multiplatform that provides modernized, fully customizable tooltips with arrows and animations.

The library solves the problem of displaying contextual information through tooltips by offering a Compose-based implementation that works across multiple platforms. Rather than relying on platform-specific popup windows or XML layouts, Balloon draws tooltips entirely through Compose, eliminating dependencies on Context, View, or XML configuration. This approach enables a single codebase to function on Android, iOS, Desktop, and Web platforms while maintaining full customization of appearance and behavior through a DSL-based API.

Developers should choose Balloon if they are building Compose-based applications that need sophisticated tooltip functionality across multiple platforms. The library suits projects targeting modern Kotlin Multiplatform development where a unified tooltip solution is preferable to platform-specific implementations. For teams migrating from earlier versions, the tool maintains a View-based implementation at an older version, though the current architecture is built entirely on Compose.

The project typically responds to issues and pull requests within one to two weeks. Development activity centers on release preparation and Compose-related enhancements, with the issue tracker dominated by release-tracking and Compose-specific work items.