The way I read @craigraw’s feedback on Github is that the criticisms are more than pragmatic. He has a list of drawbacks. The lack of fountain encoding and well defined type structures (for example output descriptors) are the biggest gaps between UR and BBQr.

Many wallets like Blue Wallet, Nunchuck, and Green Wallet have adopted the BC UR standard. I don’t see what BBQr brings to the table for users of animated QRs. It doesn’t appear to solve anything for the end user over BC UR. What am I missing?

I’m not saying that BC UR is perfect. I could come up with a long list of things I wish were different about the BC UR standard. 

 Make a list of things you with BBQr would have on the issues and we can see if we can address them :) 

 Fwiw I don’t think any dependencies are required for BC UR if you limit the scope of data types. Not even CBOR is required if you just transmit txs and psbts. 

Would like to see a clearer, technical explanation of why it’s so problematic to implement.