Thanks for the reply @DTS Engineer. For my project, using Swift is not really an option for now. My stack is more C++/Objective-C based, and so gRPC-Swift and SwiftNIO are not ideal. From what I gathered, there isn't an equivalent or other alternative that would enable this for Objective-C. There is grpc-ios, but, without going into details, it doesn't really make sense to use that either, I'm looking for a lower level framework. I see two options for me: Use the Network framework and take care of the whole TLS handshakes, HTTP headers, etc and obtain my trailer support that way. Use libcurl, which would do a lot of that for me and get trailers from there, as it supports it. Option #1 is a huge lift and would mean a lot of maintainability problems in the future. Option #2 is a bit safer, but I'm afraid of it contradicting your statement: "make sure to use Network framework as your underlying transport, because that ensures that your app will do all the usual things expected on Apple platforms". Does this mean there could be certification problems for my app if I was to use libcurl? Are there any specific guidelines I can look at to confirm this wouldn't be a problem? If libcurl isn't an option, are there known objective-c alternatives that do not force us to implement the whole HTTP/2 stack ourselves? Thanks again!