top of page
Search
Writer's pictureStuart De Ville

Should We Save Mobile Games?


I recently wrote this piece for PocketGamer, can we, should we, preserve mobile games?…


It’s easy to feel preserving mobile games stands as a vital pursuit, given their profound cultural and historical significance.


However, amidst the challenges posed by diverse hardware, evolving technologies, and poorly curated mobile game stores, a thought-provoking question arises: Do we need to worry about saving them at all?


While new technologies like Augmented Reality (AR) and Virtual Reality (VR) may usher in transformative changes, it's essential to consider the implications for mobile game developers and the landscape they inhabit.


The dynamic interplay between preservation efforts and technological advancements can impact developers' livelihoods and their studios' future.


As we delve into the realm of AR and VR, the traditional concept of preservation might expand to encompass not only the games themselves but also the innovative development processes, design philosophies, and cultural influences that shape the mobile gaming landscape.


By preserving these facets, we honour the past and equip future developers with a wealth of knowledge and inspiration.


The process of preserving mobile games, whether in physical terms or as historical resources, lays the foundation for a continuous cycle of inspiration, fostering an environment where developers draw from the past to forge new pathways of creative exploration.


In the end, the evolution of the gaming landscape is both an ode to the past and a gateway to the future. As the industry navigates change, guided by the preservation of its rich heritage, it embarks on a journey of perpetual reinvention, ultimately driving innovation, sparking creativity, and propelling the gaming ecosystem to new horizons.


What do you think? Should we be preserving mobile games?


Link to the full article:



0 views

Recent Posts

See All

Comments

Couldn’t Load Comments
It looks like there was a technical problem. Try reconnecting or refreshing the page.
bottom of page