{"id":3444,"date":"2021-08-10T09:57:00","date_gmt":"2021-08-10T15:57:00","guid":{"rendered":"http:\/\/blog.mediafire.com\/?p=3444"},"modified":"2021-08-10T10:08:10","modified_gmt":"2021-08-10T16:08:10","slug":"mediafire-2021","status":"publish","type":"post","link":"http:\/\/blog.mediafire.com\/2021\/08\/mediafire-2021\/","title":{"rendered":"MediaFire 2021"},"content":{"rendered":"\n
TLDR; MediaFire launched a brand new set of web and mobile apps! You might not have noticed, except for some significant performance improvements, because they look just like the old ones. Under the hood, however, this is a huge upgrade – these “MF2021” apps represent a major improvement to our development environment and our ability to quickly develop and release new features and updates.<\/em><\/p>\n\n\n\n It’s hard to believe it’s been 15 years since MediaFire launched its original web app in 2006! Our small team has managed to grow and evolve the service through several iterations on an ever-growing frontend codebase of mostly PHP and Javascript (jQuery). As you might imagine, through 15 years of continuous development our product and codebase became bloated, slow, and difficult to develop on and maintain by modern standards.<\/p>\n\n\n\n Over the past few years it became increasingly clear to us that we needed a modern frontend framework solution that would make our development work more efficient while also providing a great user experience in our end-product. To this end, we made the decision to transition our entire front-end codebase to React \/ React Native and began the process of slowly rebuilding all of our website and mobile apps (Android and iOS) on an entirely new shared MediaFire frontend codebase that we\u2019ve dubbed \u201cMF2021\u201d.<\/p>\n\n\n\n So, why did we choose React \/ React Native to rebuild the MediaFire apps? In short, mainly for the great developer ecosystem and for the ability to share and reuse core components of our code across our web, mobile, and desktop apps while providing a fast, efficient, and platform-native MediaFire experience on every device.<\/p>\n\n\n\n Over the past several months, we\u2019ve been slowly releasing MediaFire MF2021 into the public. Today, we\u2019re happy to report MF2021 is now running world-wide for all users on iOS, mobile web, and desktop and showing positive impacts to all our key measures of user experience. A MF2021 update is coming to the Android Play Store MediaFire app soon too.<\/p>\n\n\n\n So, what does all this mean as a MediaFire user? In the short-term, as a MediaFire user, MF2021 just means better website and app performance – everything within the My Files interface should load faster and look cleaner. In the long-term, it means more brand-new features and important functionality will be coming to MediaFire soon.<\/p>\n\n\n\n Here are a few of the highlights changes in the latest MF2021 release:<\/p>\n\n\n\n Now that we\u2019ve completed this transition to MF2021 for our main app interfaces, we will continue to replace a few remaining “legacy” components (like our image viewer) and finally break ground on some entirely new features.<\/p>\n\n\n\n In the meantime we will continue to improve our core infrastructure and all of the backend services that power MediaFire to ensure that we\u2019re delivering on our basic promise of fast and simple file sharing for all of our global users.<\/p>\n\n\n\n Thank you again for your continued support and for using MediaFire. We love to hear from you, so as always, you can reach the MediaFire product team on Twitter<\/a> or Facebook<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" TLDR; MediaFire launched a brand new set of web and mobile apps! You might not have noticed, except for some significant performance improvements, because they look just like the old ones. Under the hood, however, this is a huge upgrade – these “MF2021” apps represent a major improvement to our development environment and our ability…<\/p>\n","protected":false},"author":3,"featured_media":3447,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false},"categories":[10,25,11,2],"tags":[58,59,60,29,19],"_links":{"self":[{"href":"http:\/\/blog.mediafire.com\/wp-json\/wp\/v2\/posts\/3444"}],"collection":[{"href":"http:\/\/blog.mediafire.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.mediafire.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.mediafire.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.mediafire.com\/wp-json\/wp\/v2\/comments?post=3444"}],"version-history":[{"count":0,"href":"http:\/\/blog.mediafire.com\/wp-json\/wp\/v2\/posts\/3444\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/blog.mediafire.com\/wp-json\/wp\/v2\/media\/3447"}],"wp:attachment":[{"href":"http:\/\/blog.mediafire.com\/wp-json\/wp\/v2\/media?parent=3444"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.mediafire.com\/wp-json\/wp\/v2\/categories?post=3444"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.mediafire.com\/wp-json\/wp\/v2\/tags?post=3444"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n\n\n\n