martijnwalraven

Thanks! Especially loved the cognitive neuroscience references.

For context, I'm working on a browser and note taking app for the iPad and have been exploring ways to organize browsing activity to go beyond treating tabs as ephemeral state. It's not quite there yet, but it would be great to hear what you think once I have more to share!

I would be interested in hearing more about your tab reorganisation ideas, because I definitely recognize the pain of not being able to reconnect to a train of thought and have been exploring solutions myself. Is the research paper you mentioned available anywhere?

I wouldn't call that an architectural limitation, but you're right the default network transport in Apollo iOS doesn't currently support your use case. You can plug in your own network transport implementation however, or integrate with something like AlamoFire for example. I'd definitely like to make this easier and document it better, but I don't think it's a good reason to avoid Apollo or GraphQL altogether. I'm not sure which issue I closed before, but please reopen it if you want to discuss this further and make the client work for you!

I'm one of the developers of the Apollo iOS client, so I'm definitely interested in hearing your feedback. I know we're missing some features compared to the JavaScript client, but both the Android and iOS clients seem fairly stable and are used in production. I'm especially intrigued by the need for a 'custom mutex and other painful tricks'. Maybe this isn't the venue for detailed discussion, but please open an issue on one of the repos or post a message on #android or #ios on the Apollo Slack so we can dive into this further!