Yes! Although please note that the version at wolfia.com is more sophisticated and use embeddings to retrieve contextual snippets of code, vs this open source tool doesn't require indexing your codebase and instead leverage Open AI functions calling to let the LLM browse the code.

Thanks for the clarification. I was confused since the About link at the top of the linked-to repo has the URL https://wolfia.com prominently displayed. Both projects are very interesting and cool. Thanks!

Thanks for the feedback, we're looking into it right now!

It should be fairly straightforward for us to provide that option.

This is good feedback, we will definitely update the description. Is "A mobile app emulator you can share with a link" clearer as a first sentence?

We do not support iOS yet but yes, the plan is to use the simulator.

Oh nice! Looks like it was mostly used as a marketing tool which is a use case we're considering. Do you happen to know more about them?

I came here to see if anyone mentioned Kickfolio :) They ended up changing their name to App.io at one point. Smart, great group of folks. Closed down back in like 2015.

Interesting, what use case do you have in mind for EAs?

Totally true that TestFlight / Play Store uploads are available within 15 min, but in our experience, nobody wants to push to those platform that frequently, and force many upgrades of the app every day, so instead they do nightly builds at best. More importantly, it doesn't help if people don't have the right phone. We would love to help you with this use case, does an emulator in the browser works for you or do you need to install to phones?

For me, an emulator solves the 80% case: I'm soliciting quick feedback on specific changes. I'd happily use one as TestFlight for dev builds. I'm optimistic my users (my team) would find it more convenient, less interruptive. I'll ask them.

The other 20% is stuff that doesn't work in an emulator. Usually Apple, certificates.

It's enough of a minefield that QA means real devices, unfortunately. Used phones are vastly cheaper than "false alarm" bug reports.

> in our experience, nobody wants to push to those platform that frequently, and force many upgrades of the app every day, so instead they do nightly builds at best

If my team's big enough for daily builds, we have continuous deployment (Fastlane or similar). Strictly speaking, the pain is the build step (slow; can be flaky), not pushing the artifact.

I hope this is helpful. Feel free to dig deeper, I'll keep an eye on this thread.

Thanks for the feedback, and let us know if your team is interested.

For the deployment, wolfia allows you to share builds before they are merged and solicit feedback from your team earlier. If you think about it, the feedback loop is much faster in practice than waiting for deployment and then getting the feedback. However, I do agree that the build step is a pain! Our vision is to bring the same experience web developers have to mobile essentially, so we'll take a stab at it in the future :)

I think many commenters here haven’t been a mobile engineer at a large company- most engineers don’t have creds to manage the app for the face of a +50B company.

Yes it works on mobile but is a bit slower, we want to continue to improve performance there. It's reasonable on a Pixel 6 pro, I'm curious which phone are you using? We'll look into the ping time.

It's a Samsung Galaxy A52s, I tried Firefox and Chrome.

Also used a TCP ping app to check what seems to be the demo server - node1.wolfia.com? Average was around 160ms, ranging from 70 to 300ish, so I guess that was the real issue!

I'm located in UK and using a 4G network. Might try it again tomorrow from work and see how it compares.

Ah yeah that's probably why, our servers are only on the west coast for now, we'll add more locations in the future.

Thanks! We are hoping to support iOS within a couple of months. We want to have the same level of performance as what we achieve today with Android. I am curious what didn't work great when you tried iOS in the cloud options in the past? Just performance or something else as well?