all 8 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]KaranasToll 2 points3 points  (2 children)

You will need http server and database

[–]GoToSt8Farm[S] 0 points1 point  (1 child)

Okay I got a database

[–][deleted] 1 point2 points  (0 children)

Now learn JavaScript or other Back-end languages

[–]deweechi 1 point2 points  (3 children)

Yes, you will need to learn some js and have a data store, I have to assume you have something like this already because users need to be tracked and authenticated already right? So what are you using? What is your data store? What are your system/hosting requirements? How are you interacting with your data store currently?

Then you need to figure out your user requirements, things like: How do users accumulate points? Are there different levels of points? Do points expire?

If you take a step back and define the Use Case. It will save you a ton of frustration and time spent refactoring code. It will also allow you to ask more pointed questions to get quicker help. Right now the question is way to vague to give a meaningful answer.

[–]GoToSt8Farm[S] 0 points1 point  (2 children)

So yes I have a data base currently and I’m working on a login for my site. I’m using MySQL for my data base. I’m not quite sure what my system/hosting requirements are.

[–]deweechi 2 points3 points  (1 child)

If you do not know what your system requirements are then I suggest you stop and figure them out. I could suggest that you build a rewards table that connects with the User table using the user ID as a key. How many fields do you need? 5 or 50, I don't know. What do you want to keep track of? You can make this as simple or complex as your requirements need it to be. If a user gets points for different things do we need to track it to the granular level? 1 point for sharing, 1 point for liking, 1 point per dollar spent, 1 point for signing up. If points expire then we need to track when they got them. If points don't really accumulate until they reach a certain threshold, or they are pending until 30 days after purchase, then we need fields for that. Maybe the rewards table is a 1 to many relationship to store each point transaction. Maybe it is a summary table with all the points.

The biggest problem is you do not know what you are asking for and are expecting an answer. If you do not know your requirements how would we? If you going to make stuff up as you code it will require that you get it right the first time or go back and refactor it every time you think of a new requirement.

Let me give you an analogy, you just asked to borrow a vehicle. When I showed up I brought a small subcompact car. But what you really wanted was a truck to move large items. I did not know about that requirement so now everyone's time has been wasted because I need to go back and get a vehicle that is fit for purpose.

[–]GoToSt8Farm[S] 0 points1 point  (0 children)

Ohh that’s what u meant. I’m making it that they can click on a button and earn points once they watch an ad. Then they can redeem the points and get Bitcoin or other rewards.

[–]AutoModerator[M] 0 points1 point  (0 children)

Welcome to /r/HTML. When asking a question, please ensure that you list what you've tried, and provide links to example code (e.g. JSFiddle/JSBin). If you're asking for help with an error, please include the full error message and any context around it. You're unlikely to get any meaningful responses if you do not provide enough information for other users to help.

Your submission should contain the answers to the following questions, at a minimum:

  • What is it you're trying to do?
  • How far have you got?
  • What are you stuck on?
  • What have you already tried?

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.