Yahoo! Developer Network Blog

« Previous | Main | Next »


January 2, 2007

What's on your 2007 YDN Wish List?

Now that 2007 is here, it seems like a good time to think about the next 360 days or so. It's not that we don't have any plans for this new year, but we don't always know about the burning need you have for a new API, feature, function, tutorial, etc.

So, what would you like to see from the Yahoo! Developer Network in 2007?

  • Are there Yahoos you'd like to meet?
  • Code you'd like explained?
  • Missing APIs?
  • More examples of what other developers are doing with our services?
  • A t-shirt?
  • A pony?

Drop a comment below. We'd love to know what's on your wish list.

Jeremy Zawodny

Posted at January 2, 2007 8:11 AM | Permalink

Bookmark this on Delicious

Comments

Hi,

I'd like some new APIs to access media properties (Y! Movies, Y! Music...). Also, it would be very nice if you could bring more consistancy in your various APIs (for instance, you could implement the parameter "output" - to specify JSON, serialized PHP... - in all services).

Cherry on the cake for PHP writers that are very very lazy: provides some PHP classes to call and *deserialize* response of services (yes I know, but I always want more ;) ).

Nicolas

Posted by: Nicolas Leroy at January 2, 2007 8:49 AM

A Yahoo T-Shirt .... ne time :-)

Posted by: Ankur at January 2, 2007 9:09 AM

I'd like to see the same attention to syntax in the YUI animation library as in the others... missing semicolons and curly braces wreak havoc on certain compression algorithms, such as Dean Edwards' "Packer". Most of the YUI is fairly clean now, but animation.js is still chock full of one line if's.

Posted by: Tim Tripcony at January 2, 2007 9:21 AM

How about enabling developers to develop *on* Yahoo, apart from developing *using* Yahoo!? Is there a GData analogue planned? Can all yahoo internal data be represented in a common format? Will it be made accessable via a secure authentication api? The question is will be talk about the "Yahoo! operating system" in the future.

end of rant! :-)

Posted by: Sumit Chachra at January 2, 2007 10:07 AM

I agree with Sumit. The ability to interact with Y! services would be ideal to me. An API to send and receive Y!Messenger messages. An API to interact with Y!Calendar. Etcetera.

I'm a bit pessimistic about this though, as a former Yahoo! I watched the Y! culture (which would have energetically supported ideas like this) vaporize when marketing got involved in decision making. Its worth mentioning though. The direct interaction with Y! products and services is what I'd like to see.

Posted by: jeremiah johnson at January 2, 2007 11:13 AM

I would love a Yahoo! shirt ;-) A tie would be nice too. A fantasy football API would be better than any of those though, pleeeeeease!

Posted by: Rush at January 2, 2007 11:47 AM

I'd like a pony in a t-shirt. But seriously I think it is time to get a bit of a conformity into the different APIs or a tool that collates the output of each and brings out a format that includes most data. Right now it can be rather tiring to have amazingly easy APIs like the Answers one and others that require PHP and cURL to work properly (like flickr if you want to do more than just display the latest 20 pics by user or tag).

Posted by: Chris Heilmann at January 2, 2007 12:11 PM

Seeing as you've asked, how about SPARQL endpoints on all datasets - general search, movies, music... Shouldn't be too difficult, given tools like D2RQ, and would through the mashup potential wide open.

Posted by: Danny at January 2, 2007 12:36 PM

i wud like to hav a t-shirt as well as a pony.. it wud b kul.. n ya 1 more thing " reduced rates to call to othe countries" bcoz ther r services givin low rates .. so y wud ny1 use yahoo to call??

Posted by: shazia at January 2, 2007 2:30 PM

For the Image Search API, is there a way to specify search by image size (e.g. wallpaper, large, medium, small as on the image search website itself)?

Thanks for the feedback venue!

Posted by: Chao Lam at January 2, 2007 2:58 PM

I would like a custom search API for building custom search engines like google's. I would like it to be accessible via REST or other webservices API. I also agree about being able to tie into other Yahoo services.

Posted by: Steve Severance at January 2, 2007 5:38 PM

I'd still like to see a ColdFusion developer center. (And I'd be more than willing to help out with it.)

I'd also like to see more feedback from the team members on the forums. For example - myself - and others - have found issues with the Song Search, and have posted questions, but haven't gotten any responses yet.

Posted by: Raymond Camden at January 4, 2007 4:33 AM

Hi!

Please release FLEX 2 API for Yahoo! Map :D

Posted by: vinvega at January 4, 2007 6:25 AM

A Yahoo! Music Web Service API.
The YUI cleaned up so it's as easy to work Script.aculo.us.
Better "Related Search" results.
A few more howto's for the Yahoo Authorization API.
And a T-Shirt.

Posted by: Jay at January 4, 2007 11:40 AM

a) You release a PAID API.
With your free 5,000 queries/day usage limit, except mockups I do not know what can be do of serious. We do not only work to show our projects to family and friends.

b) You release an Overture keyword suggestion tool PAID API.

Posted by: Francois Carrillo at January 4, 2007 4:28 PM

Hi There,

It would be nice if you can give the API features like,

1. Being able to set AudioIn, AudioOut Devices as needed
2. Voice Call Events (RINGING, CONNECTED, BUSY, etc...)

Thanks,
VoiceChum

Posted by: VoiceChum at January 5, 2007 12:44 PM

Hey, we've just opened The Suggestion Box and cross-posted a bunch of these wish-list items over there. Please head on over, offer feedback, and post more bright ideas!

Posted by: Kent Brewster at January 5, 2007 1:37 PM

I would love a t-shirt.

Posted by: Jason Schramm at January 6, 2007 8:00 PM

i'd like to see a java developer center.

Posted by: Ahmad Zawawi at January 8, 2007 2:10 AM

I would like to see the implementation of the new versions for the API for web search such as inlink, update notifications etc. For example, inlink can return the anchor text that was linked to the specific page.

I would also like to have a Yahoo Developer Network T-shirt :)

Posted by: Kok Chuan at January 8, 2007 4:57 AM

I'd love a YDN T-shirt :-)

Posted by: J.Raghu at January 8, 2007 8:06 AM

When will the Map API for Flex 2 be released - I really hope sooner and not later.

Posted by: Trace at January 12, 2007 4:29 PM

How about getting my dormant email account working again, minus the 90% spam that comes in? Is that worth a T-shirt?

Posted by: BillyG at January 15, 2007 3:20 AM

Would it be possible to get some true-REST APIs? Yahoo has the power to influence the industry in this regard.

You could do a T-shirt saying "REST with Yahoo!" or something. With a picture of a pony wearing sunglasses drinking KoolAid on the beach.

See my article about STREST: http://duncan-cragg.org/blog/post/strest-service-trampled-rest-will-break-web-20/

You can contact me or the 'rest-discuss' list (on Yahoo groups!) for further information... =0)

Cheers!

Duncan Cragg

Posted by: Duncan Cragg at January 15, 2007 8:35 AM

More APIs please - Calendar would be my top priority, with Addresses a close second.

Posted by: nathan at January 15, 2007 12:47 PM

Like a lot of people I would really really like to have access to Yahoo's calendar and Yahoo Messenger.

Adding more Ruby support doesn't hurt either...

Posted by: Brian at January 16, 2007 12:12 AM

More support on ydn-auth and more development on the web service itself. Other than that the developer network has been awesome in 2006, really good work guys.

Posted by: Greg at January 16, 2007 11:03 AM

More Ruby support? Can you give examples of what else you'd like to see?

Posted by: Jeremy Zawodny at January 16, 2007 11:03 AM

Please! Flex 2/A3 version of the Yahoo maps API! Its THE only mapping component that Flex 2 people can really use. To accelerate RIA we NEED these maps! (I am aware of the Flash localConnection work-around...it works most of the time, but not all the time....I'll send you a Starbucks Card with a year's worth of coffee on it if this can get done in the next two weeks! (not kidding...)

Posted by: steve at January 17, 2007 6:50 PM

I would love to have an API for Y!Calendar and Y!AddressBook. And I would love a rich text editor as part of the Yahoo Control Library.

Posted by: Keith at January 23, 2007 7:08 PM

A Calendar API, a Calendar API and a Calendar API. Please!

Posted by: Frederik at January 25, 2007 10:39 AM

Flex 2 api for yahoo maps please

Posted by: David at February 8, 2007 7:07 PM

Flex 2 API for Yahoo! Maps.
Much needed.

Posted by: Manish at February 10, 2007 1:54 AM

API for address book and calander! Or just syncml in general.

Posted by: dave morrison at February 14, 2007 10:32 AM

A Flex 2 API for Yahoo! Maps is really needed...

Posted by: Dugast Pierrick at February 15, 2007 2:31 AM

I also think that it's very necessary...

Posted by: theklue at February 19, 2007 8:55 AM

Add my vote for Flex2/AS3 Y!Map... free us from the flash8 "IDE" please!

Posted by: jconley at February 19, 2007 1:57 PM

Please, I need the yahoo's map Flex 2 API... PLEASE!!!!!!!! :-)

Posted by: Burzum at April 3, 2007 7:06 AM

Thank you.

Posted by: Web Tasarimi at October 16, 2007 6:34 AM

A fantasy football API, especially with the ability to view the past year's draft results.

Posted by: Nathan at November 30, 2007 7:49 AM

fantasy football api!

Posted by: jon at July 28, 2008 12:31 PM

Post a comment

Comment Policy: We encourage comments and look forward to hearing from you. Please note that Yahoo! may, in our sole discretion, remove comments if they are off topic, inappropriate, or otherwise violate our Terms of Service. Fields marked with asterisk '*' are required.

Remember Me?

Subscribe

YDN Blog: Get Yahoo! Developer Network Blog on your personalized My Yahoo! home page.

Add To My RSS Feed

YDN Link Blog: Get Yahoo! Developer Network Linkblog on your personalized My Yahoo! home page.

Add To My RSS Feed

Recent Readers

Copyright © 2010 Yahoo! Inc. All rights reserved. Copyright | Privacy Policy

Help us continue to improve the Yahoo! Developer Network: Send Your Suggestions