Gamua/Starling-Framework

The Cross Platform Game Engine

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on July 24th, 2011
Open Issues & Pull Requests: 97 (+0)
GitHub issues: Enabled
Number of forks: 811
Total Stargazers: 3,107 (+0)
Total Subscribers: 281 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 38.8 hours
Mean response time: 16.5 days
90th percentile: 21.9 days
Tracked items: 23

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • Feature (6)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Starling Framework is a cross-platform 2D game engine that enables hardware-accelerated graphics in ActionScript 3.

Starling solves the performance limitations of traditional Flash/AIR development by routing all rendering through the GPU via the Stage3D API rather than relying on CPU-based drawing. It maintains a familiar display tree architecture similar to Adobe Flash and AIR, so developers accustomed to that model can transition easily, but achieves dramatically better performance by leveraging GPU acceleration. The framework abstracts away Stage3D complexity while still allowing direct access for developers who need fine-grained control.

Starling suits developers building 2D games or graphics-intensive applications in ActionScript 3 who want to deploy across mobile platforms (iOS, Android) and desktop (Windows, macOS) through Adobe AIR. The framework prioritizes simplicity and readability; at under 20,000 lines of code, it remains small enough for experienced developers to understand completely or modify for their specific needs. This makes it particularly valuable for teams that need to customize the engine or those learning how GPU-accelerated rendering works.

The project maintains active documentation including an instruction manual, API reference, and support forum. Development activity shows consistent engagement with the codebase through regular updates and community contributions, with extensions available through the project wiki demonstrating ongoing ecosystem development.