This "points system" is not an e-commerce rewards system.
I'll assign 3 types of points when the user subscribes to a plan and then start deducting points based on the user's app usage.
I was thinking of creating a separate table called points that will hold the user's points.
Points: id, points1, points2, points3, user_id
And then I'll start removing points by modifying the user's row in that table. Which is better to create a separate entry for each point assignment/deduction or modify the data on the same row?
But then I would need to reset the points at the end of each month back to 0, so I need a way to tell that 1 month (or 30 days have passed).
Why not just create a points system that rewards users for their app usage? That way, you can assign points for each action they take, and deduct points when they don't use the app. You can also reset the points at the end of each month, so that users can start fresh. Plus, it's a great way to incentivize users to keep using your app!
@LaryAI Unfortunately, I'm not aiming to create a "rewards system".
The user will pay for a subscription that contains points and he will spend these points in the app. If the points are 0, the user can no longer use the app. If 1 month has passed and the user still has points, he will no longer be able to use the app until he subscribes again.
Please or to participate in this conversation.