Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9252471
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 18, 20262026-06-18T10:57:10+00:00 2026-06-18T10:57:10+00:00

Some people have asked similar questions about protecting HTML5 apps and protecting freemium apps,

  • 0

Some people have asked similar questions about protecting HTML5 apps and protecting freemium apps, but not both together. I’m asking this separately because I have the impression (whether right or wrong) that HTML5 is particularly insecure vs native.

I’m working on an embedded HTML5 app I want to monetize using the freemium model, but I’m worried about how to keep its virtual currency and scoring variables from being too easily messed with by the end user, as I fear this could negatively impact revenue if some hacker (no offense intended by the term) were to create a YouTube video or blog posting about an exploit. I think it is pretty unlikely early on for this to happen, but I think vulnerability will matter more with popularity. I’m also worried about with which someone can copy an app.

I though realize both are possible inherently with an app installed on the device.

My questions are:

  1. How easy is it, in your opinion or experience, to mess with an
    unobfuscated embedded (not browser dependent) HTML5 app and its Javascript vs a native app with core files based on Java or Objective-C data?/How well does obfuscation work on HTML5 apps vs native obfuscated
    apps in terms of data protection?
  2. How difficult is it to obfuscate an HTML5 app vs using something like Proguard on regular Android apps?
  3. Does obfuscation cause HTML5 to noticeably slow down for normal users?
  4. Lastly, do you think it’s practical to have an HTML5 app with
    freemium features? Or do you personally think it is too vulnerable?

What I’m basically trying to figure out with them is whether HTML5 is particularly vulnerable or hard to protect, at least when compared to protecting native apps. If an obfuscated HTML5 app is as secure or insecure as a regular app, then I guess I’m okay with it.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-18T10:57:11+00:00Added an answer on June 18, 2026 at 10:57 am

    The only way to prevent cheating (and unlocking freemium items is a kind of cheating) is to move all the relevant game logic to the server. Forget about obfuscation. When it’s executed on the clients machine, it’s under the control of the user. Obfuscation can slow the user down, but it can’t stop someone who is determined to hack it. This doesn’t just apply to javascript, it applies to every game client, no matter what programming language it is written in.

    A general rule of designing cheat-proof multiplayer games is to never trust the client and do all calculations which are relevant for gameplay on the server.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Many people have asked about Rails hosting on this site, but I'm not familiar
Yes other people have asked this question before, but not in the same context
Ok, I see that people have asked this question before, but I'm seeing some
Several questions about accessor methods in C++ have been asked on SO, but none
Some people have mentioned RockScroll and MetaScroll in This Question , but those only
I know a lot of people have asked this question, but I still will
I recently asked about the location of Action Filters in MVC. Some people suggested
Okay, I kinda asked this question already, but noticed that i might have not
Looking around Google I can see a few people have asked this but there
i know some people asked the question, but no answers helped me, and i'm

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.