Thanks! Yes, or at least it will be in the future as we have not yet publicly released our SDK's for 3rd party devs :)
What sets us apart from AirConsole is our strict niche focus on real-time action party games and social couch gaming. In practice this means that the games added to our platform's public playlists should adhere to being short, competitive and real-time (no asynchronous or text/language-based trivia games).
AirConsole on the other hand is fully focused on in-car-entertainment at the moment as the whole company was recently sold to a car software manufacturer. My understanding is that they are not accepting any new 3rd party games on the platform apart from few very high-profile games based on already established studios and IP.
I've been actually kind-of enjoying using Jules as a way of "coding" my side project (a react native app) using my phone.
I have very limited spare time these days, but sometimes on my walk to work I can think of an idea/feature, plan out what I want it to do (and sometimes use the github app to revise the existing code), then send out a few jobs. By the time I get home in the evening I've got a few PRs to review. Most of the code is useless to me, but it usually runs, and means I can jump straight into testing out the idea before going back and writing it properly myself.
Next step is to add automatic builds to each PR, so that on the way home I can just check out the different branches on my phone instead of waiting to be home to run the ios simulator :D
Im not sure about how this translates to react native, AFAICT build chains for apps less optimiside, but using vercel for deployment, neon for db if needed, Ive really been digging the ability for any branch/commit/pr to be deployed to a live site i can preview.
Coming from the python ecosystem, ive found the commit -> deployed code toolchain very easy, which for this kind of vibe coding really reduces friction when you are using it to explore functional features of which you will discard many.
It moves the decision surface on what the right thing to build to _after_ you have built it. which is quite interesting.
I will caveat this by saying this flow only works seamlessly if the feature is simple enough for the llm to oneshot it, but for the right thing its an interesting flow.
I hooked up a GitHub repo that's long been abandoned by me and I've just been tinkering with menial stuff - updating dependencies, refactoring code without changing any actual implementation details, minor feature or style updates. It mostly works well for those use cases. I don't know if I'd give it anything important to develop though.
This is exactly why we built superconductor.dev, which has live app preview for each agent. We support Claude Code as well as Gemini, Codex, Amp. If you want to check it out just mention HN in your signup form and I’ll prioritize you :)
I live in Switzerland and am (like many people here) an avid hiker. There are a lot of great hiking websites but they all suffer from the same problem: They are ultimately just a list of hiking routes that you need to plan around.
Because I do a hike almost every week, the extra planning has become an overhead that takes time out of my life: how far away is it, what train should I take, whats the weather situation like, do I need to bring snowshoes, etc. The 65,000km of trails in this country also gives me decision paralysis!
So I'm building an app (React native/django) which takes a users current situation and preferences and then algorithmically suggests a few best options for them that they can quickly give a yes/no to. It's integrated with a lot of data like the train timetables, snow data, weather forecast etc.
I was able to reduce an hour of planning down to 5 minutes last week, so it's definitely working for me. What I am currently trying to do is figure out if other people have this problem and there's interest in the app concept.
This sounds great! My partner and I also spend a lot of time just scrolling around the Swiss hiking maps looking for potential routes. I had an idea for better filters (e.g. roundtrip hikes with >1000m elevation <2h by transit) and got as far as displaying hiking and transit data. Are you looking for testers? :)
Interested...from Italy!
some "hike with kids" filters could be interesting too.
I don't have much time at the moment, but if you need an help let me know (even just for brainstorming)
Pretty sure people would want to play with it here in Geneva but it would need to expand to covering the French, Italian and Austrian Alps too over time. Keep us posted.
Can you elaborate a little on what you don't like about Rancher?
Have been looking at moving my org over to it (30 engineers), seems quite nice so far - built-in in k3s is great and it works well on my macbook
Its docker drop in support is lacking. There are instances where I expect it to do something and it errors or does something bizarre.
The interface is very basic. I had to get plugins for very basic functionality that has been built into Docker Desktop for years, like Logs Explorer.
It seemingly always prompts for Admin Access on the computer, even though Docker long ago stopped doing this and has worked without admin access for some time.
The prompt for enabling admin access is funny. If you don't have it already, it will prompt you to enable it, if you have it enabled, it will pop up another window, very similar, and the wording will say "Startup Rancher Desktop without administrator access" but its easy to miss the wording difference, cause the font is small.
I've had stability issues, containers randomly crashing or the daemon going down out of nowhere. Happened more than once.
It claims to be a drop in for Docker CLI, but while I don't have the list handy at the moment, I know this isn't true, particularly with docker-compose
I could go on, but its still really rough around the edges.
