A sudden update by Instagram to remove the vertical scrolling feature and replace it with the horizontal feed has been infuriating. There have been certain conjectures made to bid farewell to the social networking app and the users have expressed their resentment on Twitter and other platforms about this sudden and instantaneous change.
According to reports by the Head of Instagram Adam Mosseri, the event was actually a small and infinitesimal experiment but it went further than expected. TechCrunch had been the first to officially report about the reshaping and redesigning of the app in October probably via their sources. However, that experimented internally within a closed circuit on the app’s Explore page.
I have the new Instagram horizontal scroll interface. I’m sure this will not be met with any backlash WHATSOEVER. But seems maybe intended to reduce mindless vertical scrolling? cc @mosseri comments at the end 😭 pic.twitter.com/fwmtbfjFaf
— Alex Heath (@alexeheath) December 27, 2018
Everyone on Instagram today when their timeline briefly changed to sideways scrolling pic.twitter.com/NFhHcfFmEn
— Marques Brownlee (@MKBHD) December 27, 2018
On Thursday, the company tried to apply the experiment to the main feed which enabled the users to only swipe to left and right without being able to scroll up and down which had been the only way to use Instagram since its inauguration. The sudden change in the popular photo-sharing app annoyed the users and they showed their grudge on Twitter.
This new Instagram update pic.twitter.com/9rzcn607uF
— Zara Larsson (@zaralarsson) December 27, 2018
Instagram development team#instagramupdate pic.twitter.com/zX1W2ITb4K
— IGZ (@igzrap) December 27, 2018
https://twitter.com/esmemeh/status/1078351197717839874
Due to a bug, some users saw a change to the way their feed appears today. We quickly fixed the issue and feed is back to normal. We apologize for any confusion.
— Instagram (@instagram) December 27, 2018
Soon after the bizarre incident Instagram officially apologized for the mistake and its team quickly fixed the bug which caused the issue.
