Instagram Testing Full-Display screen Feed, Will probably be Out there to Customers Quickly

Instagram is testing out a brand new full-screen feed on its picture and video sharing app. The social media platform has confirmed the identical through a Tweet. CEO, Mark Zuckerberg, has additionally shared a preview of the full-screen feed testing on his Instagram story, citing that the ‘images are nonetheless an necessary a part of Instagram’. Furthermore, this new look of the Instagram feed will extra doubtless appear to be what’s stated to come back on TikTok. The complete-screen model of the Instagram feed will probably be out there to all customers quickly.

Instagram has introduced the testing model of the full-screen feed on the platform through a Tweet. Then again, Meta CEO Mark Zuckerberg additionally shared a preview of the full-screen feed on his Instagram story. The upcoming full-screen model of the feed is at the moment beneath testing and is more likely to be made extensively accessible quickly to the customers, in response to the corporate.

The brand new look additionally appears to tweak the shortcuts for accessing the messages inbox and creating new posts on the platform. This new look of the social media platform is alleged to be much like what TikTok Clear mode, which was reported to be in testing earlier this month.

In the meantime, Instagram customers have been lately affected by a difficulty on the app that repeatedly confirmed older tales shared by individuals they’re following, even after viewing them. The platform was affected by a bug that trigger the app to point out beforehand shared tales as a substitute of instantly displaying the most recent ones, in response to consumer stories. The bug was affecting customers on the Instagram app for Android and iOS. Customers have been reporting that they have been compelled to look at tales that they’ve already seen.

Fortunately, the corporate launched an replace aimed toward fixing the repeating tales bug on its iOS app. The brand new replace — v239.1, reportedly resolved the stated bug.