If you're consistent about not sending values if a...
# spring
k
If you're consistent about not sending values if an element is null, I still don't see an issue. Your JS clients will learn to look for undefined. Your Android clients will treat it as null. Your iOS clients will also treat it as missing. Consistency is what API consumers want IMHO