Biased towards web projects. Please support iOS and Android mobile apps, Unity videogames, and desktop native apps.

[Emasoft]

Codesight is too biased towards web projects. Please support iOS and Android mobile apps, Unity games, and desktop native applications ecosystem.

[Houseofmvps]

Fair challenge — some of this exists already, some of it is a real gap. Current state in v1.19.0:

Already supported:

• iOS/macOS: Swift AST extraction — SwiftUI views, Vapor routes, workspace detection for Package.swift in subdirs
• Android: Kotlin AST extraction — Retrofit routes, Room schemas, Jetpack Compose components, Navigation graphs, activities from the manifest
• Flutter: Dart extraction — widgets and routes
• Desktop (partial): C# extraction covers ASP.NET, and Electron apps work through the regular JS/TS path
• Roku: BrightScript/SceneGraph (shipped via Support for Roku projects (BrightScript, BrighterScript, SceneGraph) #36)

If you ran codesight on an iOS or Android project and got thin output, that's a bug I want — open an issue with the project layout and I'll treat it like the others.

Real gaps, agreed:

• Unity: no MonoBehaviour/ScriptableObject/scene-graph awareness — the C# extractor treats it like generic C#
• Native desktop: no WPF/WinUI XAML, no Qt/GTK

Unity is the strongest candidate of these (huge ecosystem, well-defined conventions: components on GameObjects, serialized fields, scenes/prefabs as the "routes" analog). I'm keeping this open as the roadmap issue for that. If you have a specific project type in mind first — Unity vs native desktop — say so and it'll set the order.