A huge thank you to the Sprinqua team for being the first external developers to build and publish an application for Orbit OS.

It’s great to see Orbit OS starting to grow into an open ecosystem where external teams can contribute real, working solutions. Sprinqua is a strong example of what can be built on top of it, and it marks an important step toward a more open and extensible platform.

You can find more about Sprinqua on their official page:
www.sprinqua.com

Sprinqua app available here:
https://store.orbit-os.org/app/sprinqua

Before posting a troubleshooting request, what logs and diagnostics should we include to speed up support?

I want to follow best practices and provide enough technical detail from the start.

My install failed because I selected a package for the wrong architecture.

After selecting the correct build for the target board, installation succeeded immediately.

Posting this in case it helps other newcomers.

Sharing a solved issue: package download timed out on first boot.

Root cause was incorrect DNS on the gateway side.
After fixing DNS and retrying, everything installed correctly.

Can we keep a standard troubleshooting checklist for new setups?

I currently verify network, DNS, time sync, package endpoint, and free disk space.

Would love to add any missing checks from experienced users.

Is there currently any app available for iOS? I would like to use OrbitOS services from an iPhone.

Would it be possible to create a VS Code extension for OrbitOS development workflows?

It would be very helpful to have project templates, deployment helpers, and quick diagnostics directly in the editor.

I just finished installing OrbitOS on an Arduino Uno Q setup and it is spectacular.

It feels very lightweight, responsive, and stable.

Everything I tested so far works really well. Great work by the team.

I am considering using this OS on an industrial board that runs Linux, for a project involving IEC-61850 communication.

Main questions:
- real-time behavior under load
- networking stack stability
- long-term update strategy for critical systems

Would like to hear from anyone testing similar industrial scenarios.

I have an older Raspberry Pi 2 available for testing. Is it possible to run OrbitOS on it today, or are there architecture limitations?