3 ms·
Give me a break. OpenFlights.org, a completely free open-source flight mapping tool, had a really popular Facebook app that a) let people post a map of their f
by jpatokal 14y ago
Give me a break. OpenFlights.org, a completely free open-source flight mapping tool, had a really popular Facebook app that a) let people post a map of their flights to their Facebook profile, and b) post updates on Facebook automatically when they flew somewhere -- not exactly spammy, parasitic or viral, just sharing info with friends. But merely keeping the FB app up and running consumed more support time than the (far more complicated) website itself, because the APIs changed all the bleeping time, and eventually in 2010 Facebook decided that letting people post apps they liked to their profile was Not Allowed(tm). So we gave up, and seeing what has happened in the three years since, I don't regret making that call one bit.
http://openflights.org/blog/2010/11/05/farewell-to-facebook/ http://openflights.org/blog/2010/11/05/farewell-to-facebook/
- weixiyen 14y agoThis is pretty much why I will never develop a facebook app after having worked at a company that develops apps for facebook. The push fast and break shit mentality is terrible for APIs. It's too much work, and the Mobile space has more opportunities. Just the thought of having an app inside of an iframe is silly to be honest. It's not the way products are meant to be experienced. On iOS or Android, you are in someone else's ecosystem, but at least your app takes control of the entire user interface. You cannot have that much control over the customer experience in the context of a facebook frame.
- sdqali 14y agoI am curious to know in what way have you felt that the Facebook way of rendering your app in an iframe restricts the user experience?