Hi Guys & Gals,

Just to briefly introduce myself, i.am.ron and I work with the MySpace Development Platform Content Team (YAY!)

We're in the process of working on 'what our developers want and need' in the way of documentation/content.  

I have gotten some awesome ideas from the other forums, but I thought it might be nice to open a thread for this purpose. 

We'd love to hear your suggestions and comments. As you are probably aware, we have a FAQ that we're working on as well as ways to make it bigger and better and we want your input! 

Any feedback for content is always wanted and appreciated! 

~ Cheers

Rhonda

MDP Content Team 

  

 

 

 

 

I'm sure I have suggestions, but all I want to say now is *bump*

 ...and we love the content team. woo! :D

 Not as much as we love Stephanie :)

Bump.

 

We're giving you a forum thread guys! Let's hear it :) All in one place :P

 

~ron

MDP Content Team 

Can the users of our application have a mechanism to invite users to join our app or send messages to users? At the least give us a rough timeline if this feature will be implemented. I dont need a specific date but if developers are going to spend time developing a myspace app, then they need to know if this feature will be done by the time Apps launch in March.

It would also be nice if the REST interface was explained better. Will I ever be able to write the canvas page using the REST interface?

I am a little confused by your message. Are you asking if you can invite others developers to use your apps while we are still in the 'sandbox' phase? There is a good walkthrough about this here:

http://developer.myspace.com/Community/blogs/devteam/archive/2008/02/05/let-me-see-my-app.aspx

If you are asking if other users who install your apps can share it with users other then the developer, I am not sure. I don't think this can happen until we are OUT of the sandbox phase, but I can look into it for you. 

 If I am way off base with both these answers please elaborate a bit more and I can check into it.

As for the REST interface, we are currently working on better documentation on all areas and hope to have much of it done before we go totally live in March- we are working on it. :)

I will add this question to my list and hopefully one of the developers can answer this better.

Let me know if that link helps you out. :)

Rhonda 

 

 

 Well, I guess this is the one stop shop for putting down some "info" :)

For me, knowing ahead of time, what the mechanisms will be for "sharing apps" would be very useful.  I realize opensocial 0.7 has an API call for this (to wit, Orkut says they are opensocial 0.7 but alas.. not a single opensocial 0.7 call works on their site).

As well... I mean, outside of reading white papers.. I do not yet know what "real effect" on my code Caja will have.  Can I use eval?  Can I pass functions around inside json objects, and then execute those functions?

Will the sharing api's be opensocial (i.e. javascript only), or will their be REST api calls to accomplish the same purposes?  The reason I ask, is then people could iframe their apps (to be able to dynamically change their apps on the server side/on the fly) but then still have the ability to build them one "Share this!" etc.

 I could go on and on haha..    

Glad to see you are all taking the initiative to start the discussions.  We all love the *idea* behind OpenSocial.. but due to its rather "vapory" existance.. devoting tons of development time to it is just a bit scary :) 

Rhonda, To clarify the original question--the people in this thread want to give application users to invite their friends to add the app. For example, you made a Fight Club app which allows users to fight each other. So Bob adds this app to his profile. He then decides that he wants to fight his friend Tom. In facebook there is functionality called Invites that allows you to invite a friend to install an app. The invite would say something like this on Tom's newsfeed "Bob just punched you, join Fight club and punch him back" Gene

First, I want to congrats the Myspace team on the work you are all doing to get platform out. I am sure you are all working very hard on this.

So I want to throw this in (and it is NOT meant to be a criticism at anyone specfically):

Currently, it seems the fundamental functionalities for a 'social app' are either missing or not implemented (with no real ETA). Fundamentals like bump/invites, notifications, callbacks etc.  There are 'workflows' to how a typical app may work:

- install, notify backend, announce on feed.

- user invite/bump friends, send notification, announce on feed.

etc etc 

Without many of these, it is just a static app. (3 users in a sandbox can be used to test many of these workflows - so the sandbox is not the issue)

Another issue is that the platform is based on opensocial (unproven, not baked) - so we are dealing with two tech in flux. I think the Bebo approach was very intelligient - they supported both opensocial and the FB approach. The early adopters are typically FB developers, and by wrapping the FB apis, it helped Bebo launched their app initiative very quickly.

I was at the myspace developer launch night - and I did see the demos from the usual crowd (rockyou, slide etc). So either those demos were 'mockups' or they have access to certain features that is closed to us. (As of today - I was told that activityAPI was not implemented - so I am not sure how their apps worked)

 

 Heya -

Re: communication/viral: see this - http://developer.myspace.com/Community/forums/t/115.aspx

Re: the demos. No company you saw demoing on 2/5 had access to anything more than you all have access to now. In fact, they had access to MUCH less - this site is far from perfect right now, but it has a lot more documentation than it had then, at least. I was pretty stunned that some of the companies managed to do what they did, it was really, really cool. :) I suspect some may have been using form inputs, or scraping instead of API's, but they'd need to answer that for sure (you'll find them all around here int he forums).

Re: Open Social - yes. I can't argue that it's not final, you're right, and it's still being defined. But given the option to wait for Open Social to be fully baked before launching, or launching with the stable api's we have, we wanted to get something out for people to start playing.

Re: Specific API's. As much as possible, we will provide REST api access to features.  

Re: Caja. Caja's also still being defined, as I'm sure you know. There's a bunch of documentation over on Google's site, and we'll have our own here once things are better baked in.

Hrm. I may have missed a question or two, this was a long thread - if I did, just holler, I'll answer. :)

Thanks! 

 

And not having a rendering presentation layer like FBML is painful. 

Now I have to spend time trying to develop an invite UI vs two lines of code on the other flatforms. 

I'd say the biggest missing piece overall is Flash support. I know the MDP supports SWF files, in theory, but I can't make it work and can't find any documentation at all. It would be nice if we could get a Flash starter kit to get us as far as a "hello world".

Hi, it is a great place to ask some question. Thanks for your work.

When will the api for notification, invitation, feed, email, which are provided in facebook, be available in myspace. Just like My Fun App said, they are  fundamental parts of the work flow of a social app.

Thanks in advance.