50 Apps You Will No Longer Be Able To Use With Instagram Very Soon

By Oyindamola Bamgbola

 

In the bid to create a more profitable environment for its platforms, Instagram will be cutting off a lot of third party apps.

Here are the reasons they gave for this change yesterday (November 18, 2015):

When we launched our first Instagram API in 2011, we were a very small team and knew we wouldn’t be able to build all the features our community might want. Today we are announcing several platform changes to improve people’s control over their content and set up a more sustainable environment built around authentic experiences on the platform… 

We’ve heard from the community that it can be unclear where their content is being shared and viewed…

The new simplified platform policy for developers suggests that Instagram may have patented the words “insta”, “gram” and “instagram”.

Screen Shot 2015-11-19 at 10.41.18 AM

 

Instagram further states that:

We will begin reviewing new and existing apps before granting full API access starting December 3, 2015.

Any app created before Nov 17, 2015 will continue to function until June 2016.

 

The apps circled below may be affected by this new IG policy.

 

50 (1)

No more Flipagram, InstaRepost, Textagram, Instafit? Damn.

In past weeks, Instagram has been making some really big changes just like its counterparts Snapchat, Twitter and Google+. It started out creating apps like Layout and Boomerang.

Testing the new Boomerang app by Instagram…

A video posted by ID Africa (@idafricang) on

This was followed by making an allowance for portrait and landscape photos and videos; then came Instagram ads for advertisers. Now, a new policy that forces third party apps to #CommitorCommot.

LOL.

Smart move Instagram.

 

 

Photo Credit

TechCrunch

 

No Comments Yet

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

 

FOLLOW US ON