Hi, this isn't a bug report or technical question, I'm keen to learn more about Google's approach to engineering.
I've been following Google Ads API development loosely over several years. When feed based extensions came out, I could see their potential but they also seemed too complicated for most use cases. This was apparently true for many others, as evidenced by the extensions setting services. Now that feed based extensions are being retired in favour of asset based extensions, I wonder if there's a lesson to learn here. I've seen similar features come and go in our own product; powerful, useful at the right time, but ultimately too complex for most users and too costly to support. Maybe I'm off the mark but either way I'd be interested to see a tech talk on the history of AdWords feeds; the reasons for introducing them, decisions made along the way, and the reasons they were retired. It might help the rest of us to make better informed plans. Is that something the developer relations team at Google would consider? Thank you for listening! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/db87d7ee-9a81-45e6-b06e-25ec10d9ae99n%40googlegroups.com.
