Skip to content
Menu
Developer Dispatch
  • Home
  • Game Development
    • Switching From AS3 To Swift
    • Cribbage vs Robots
    • Island Golf Development Notes
    • WindWord Development Notes
  • Technical Insights
    • The iPhone X Is Not a Good Gaming Device
    • There’s a Lot You Can Learn From 404s
    • What Flash Means
    • A Free-First Approach: Thoughts On Mobile Game Monetization
    • New and Improved Isn’t Always Better
    • WP Tips and Hacks
Developer Dispatch

New and Improved Isn’t Always Better

The Misconception of “New and Improved”

The phrase “New and Improved” often creates confusion. The term “new” is redundant because “improved” already means “better.” Therefore, “Improved Isn’t Always Better” would be a more accurate statement. However, improvement inherently means better, making “improved” always better by definition.

This thought came from a player of a jigsaw puzzle game recently converted from Flash to HTML5. During the conversion process, every effort was made to improve the game. The new version included all features of the old game, added new options, and upgraded image quality. Converting to HTML5 also made the game accessible to millions of users without Flash.

Resistance to Change

The player likely intended to express discomfort with change. Although the new game was an improvement, it felt unfamiliar to them. Subtle differences, such as the shape of the puzzle pieces, made the game seem different from what they had been accustomed to for years.

This resistance to change is a common and valid human response. As a developer, I have encountered this reaction throughout my career. Even when changes clearly improve the software, some users resist because they are attached to how things were.

The Necessity of Change

Change is often necessary, especially as technology evolves. In this case, Flash is increasingly disliked and approaching its official retirement. The move to HTML5 was required to ensure the game’s continued functionality and accessibility. If this change had not been made, in a few years, the player might have faced the situation where the game no longer worked due to the discontinuation of Flash.

Developer Responsibility in the Face of Change

As a developer, I, not the user, am responsible for adapting. While I cannot ask users to adjust to change, I can explain why it is necessary. If I cannot convince users that the new version is better, I must accept their departure. Ultimately, the improvements will benefit most current and future players, and I must press forward with those changes.

Search

Suggested Topics

  • A Free-First Approach: Thoughts On Mobile Game Monetization
  • Cribbage vs Robots
  • Home
  • Island Golf Development Notes
  • New and Improved Isn’t Always Better
  • Switching From AS3 To Swift
  • The iPhone X Is Not a Good Gaming Device
  • There’s a Lot You Can Learn From 404s
  • What Flash Means
  • WindWord Development Notes
  • WP Tips and Hacks
©2025 Developer Dispatch | WordPress Theme: EcoCoded