mikelikespie

I’m in a similar spot. I miss CarPlay much less than I expected because the Rivian software is really good. The big thing I really miss from CarPlay is having text messages announced. Google Maps on the phone is a bit better too but I got over that quickly (TTS, features like showing road hazards, and general rendering)

Thanks for following up and updating your post! Hopefully our official one is a better experience.

Also we've had a couple reports of people downloading imposter apps instead. Could you verify you're on the official Claude app by following this link? https://apps.apple.com/us/app/claude/id6473753684

Hi, Anthropic eng here. Thanks for your feedback. You should be able to use your existing account, assuming you're signing in with email, and it should share your existing subscription too. If you're still having issues, you can contact our support at support@anthropic.com

Pro users can change the default model in settings. We're working on surfacing this a bit better when starting new conversations too.

It's coming soon, stay tuned. You can join our waitlist here https://docs.google.com/forms/d/e/1FAIpQLSeA7XIFJw6ofH9FtEXH...

Hi All, I'm thrilled to share that we just launched the official Claude iOS app, which I had the chance to build as the iOS engineer on the project over the last several months. We wanted to make an fast and fun mobile-first experience for Claude. We'd love to hear what you think.

While developing Retool Mobile, our team experienced & overcame several performance challenges with React Native. This work led to some interesting learnings, and so we wanted to share with you—we hope this helps someone else!

Thanks! We're working on the map component right now, so stay tuned.

Mike, Mobile Eng Lead @ Retool, here. We support on-prem if you're on a version newer than 2.100 (which has been out for a few months). If you can reach out to your AE, tommy at retool dot com, we can get you set up with mobile in no time.

Mike here (Eng Lead on Retool Mobile). Thanks for the lovely note John! It's been great working with you throughout this process and we're really thrilled to hear how we're having an impact on your business.

It's quite nice looking. Nice job guys!

It is certainly possible to write one. All the back-end stuff can be reused.

Interactive console support is coming. We need to work out a few kinks before it is ready to go

PonyDebugger could be extended to support this very easily. We pretty much codegen "controllers" for all of Chrome Developer Tool prootocols's domain. One could map the UIView hierarchy to the DOM by just implementing a delegate.

You can look at the "*DomainController" classes here for examples: https://github.com/square/PonyDebugger/tree/master/ObjC/Pony...

For implementing DOM-like viewing it would require you to implement PDDOMCommandDelegate defined here: https://github.com/square/PonyDebugger/blob/master/ObjC/Deri...

Docs here: https://developers.google.com/chrome-developer-tools/docs/pr...

Glad to hear. If you run into any issues, please file it on the github page. We tried to simplify it a lot, but there are a lot of moving parts and we can improve even more.

The name came about because our internal HTTP library is named PonyExpress, and this tool was originally part of it. At least it is google-able, right?

Doesn't work with 6455 :(

I can't answer this yet. I'd be curious to hear

Rad! Somebody pointed out slanger to me previously, but I was unaware of PushPlay. Thanks!

Cocoa-websocket doesn't seem to support the latest standard[1]. You can tell because the handshake has key1 and key2 which is protocol 00[2]

Re: socket.IO, I haven't actually used it, so correct me if my assumptions are wrong, but the objc client doesn't seem to use WebSockets as a transport. So I imagine you can get the same bidirectional semantics if by using socket.IO-objc if you want to limit yourself to servers written in node (or have a socket.IO bridge).

However, why not go with standards? Since socket.IO supports websockets, the objc implementation could be backed by SocketRocket easily.

My two biggest complaints against Unitt & cocoa-websocket aside from them not supporting RFC6455 is having CocoaAsyncSocket as a dependency.

I've dug deep into it's implementation, and even had a prototype of SocketRocket that used it (basically went from CocoaAsync to dispatch_io to CFStream), and I'm not too impressed. Also, CocoAsync 2x or 3x more code than the entire WebSocket implementation without it. It also has drastically different codepaths for iOS and Cocoa and it's very difficult to see what's going on. Makes testing more difficult.

The other reason I decided to roll my own is just a learning experience. At first I wanted an excuse to play with new libdispatch io stuff[3].

[1] https://github.com/samlown/cocoa-websocket/blob/master/WebSo...

[2] http://en.wikipedia.org/wiki/WebSocket#draft-ietf-hybi-thewe...

[3] http://www.opensource.apple.com/source/libdispatch/libdispat...

I think it's the same reason you would want to use good old HTTP over raw sockets for a request/response API, even though with a native client you could just invent your own protocol.

If you want bidirectional communication to your app, it's much easier to make a server that uses the WebSocket Protocol (tornado, etc.) instead of rolling your own server and protocol.

The reason Unitt didn't work for us is that it isn't updated to work with the latest WebSocket protocol. This is an issue, especially since there's finally a standard (RFC 6455)

tools.ietf.org/html/rfc6455

Tornado is nice since it implements some of the legacy versions of WebSockets, but there are many servers that will probably deprecate them sooner rather than later.

This would be cool. We've been experimenting with uses for WebSockets. One of them is mocking push notifications in the simulator. The other is basically implementing a pusher-like service with a pub-sub model.

I'm unsure what you mean by "Socket.IO via an Obj-C lib". Could you send a link? It looks like Socket.IO is node (which I don't believe you can use in iOS).

Yes... BSD style FTW (aside from hard tabs I suppose) http://en.wikipedia.org/wiki/Indent_style#BSD_KNF_style

Nah, don't think so. I wasn't aware of any existing so I just wrote one. Apologies for lack of novel idea :P

Tornado isn't good enough for you? :D

I made it interactive. Let's play! Sorry I had to submit again, but couldn't have the same URL scheme. Also, batteries are running low, so I couldn't get the clicking working in FF.

Nah, just inkscape.