Ratings, or why a sex shop forum?
It's no secret that a lot of websites appear every day on the network, each of which tries to use the social possibilities of the web to its fullest : social networks appear, forums (fewer but still appear), even online stores try to keep up and enter in their projects, likes, stars, comments and other echoes of social networking functionality.
Me and my team, as web developers, often have to deal with customers who either need this or that social feature to live on the site:
')
Few customers know why he really needs such things on the site: some of them follow intuition, some follow suit, and for some it's just another Wishlist. Any social functionality is exactly the rating. In one or another of his views:
Ratings are an important component of the socialization of the Internet. Just think: we choose hosting based on ratings, making purchases in online stores (especially foreign ones) - we look at the reviews before reading the entries in blogs or social networks - pay attention to the number of “likes”, and there are also these types of ratings that contribute in the life of the user on the site of rivalry, for example, the same rating of habra people . We use them every day, without even noticing how firmly they entered our lives.
As a rule, a certain amount (or hours) is spent once on the development of rating systems for the site owner: the system is developed, implemented, and, in fact, works. It is rare when changes or additions are made to a working rating system, unless we are talking about really large projects.
The network is full of ready-made plug-ins, libraries, and simple developments for rating systems, but the customer always needs something “original”, and speaking of code copyright, one way or another you’ll have to write with your own pens.
And what if on a site besides the usual rating of one or another entity, certain achievements or statuses are needed? In this case, in addition to an additional check for revision, a check for design and creativity will roll out, and the developer will have: facepalm :, because everything will have to be sawed. Or, you will have to develop a flexible system from scratch, and you should also write an admin for the whole thing! Naturally, everything should work quickly and be considered correctly, which means testing, optimization and refactoring will be added to the above points.
In this regard, we came up with the idea: why not bring all these calculations to the cloud? At the same time build a fairly flexible system, organize an API and implement it on projects. Some of the readers at this point will think: "who would doubt another startup." My answer is yes, this is a “regular” startup.
The name of the startup - Rangg - was formed from the phrase Rank Aggregation . Now the service is in development and “touch” it, unfortunately, habrazhiteli not work. We will definitely roll out the beta within a month, and the first to know about this will be Habr.
As you have already guessed, the essence of the project is to build a cloud service rating and achievements, which could be implemented with minimal effort on the project, enable developers and site owners to build their rating systems with achievements, ranks and statuses. We have compiled a short list of functionality that will be available at the launch of the project (can be changed):
At the moment, the RESTful API is being developed (not without the help of habr posts) and the service of providing access, configuration and statistics. The technologies we use on our project are quite popular: PHP + MySQL - service, NodeJS + MongoDB - API. The next article will tell about the project architecture and the integration of these fairly well-established bundles.
In conclusion, I would like to sincerely thank the administration for providing a blog; for your part, this is a huge step in support of startups.
Turning to the hacker readers, I want to ask for constructive criticism of the project idea.
PS If you made a mistake with the hubs - tell me exactly which article would fit better, correct it (I would like to add to “Analysis and design of systems - lacked karma).
Me and my team, as web developers, often have to deal with customers who either need this or that social feature to live on the site:
- Make me a forum on sex shop
- What for?
- Well, let the people sit talking.
- They came for shopping, but not to communicate. They came to buy faloimitators - came, saw, ordered.
- Let it be. We begin to fill themselves, the people and tighten up.
')
Few customers know why he really needs such things on the site: some of them follow intuition, some follow suit, and for some it's just another Wishlist. Any social functionality is exactly the rating. In one or another of his views:
- Likes
- Add to favorites
- Comments (not only can the number of comments be equal to estimates, they also serve as feedback)
- The "share" function (unlike "likes" carries more rating points)
Rating (eng. Rating) - a numeric or ordinal indicator that reflects the importance or significance of a particular object or phenomenon.
Ratings are an important component of the socialization of the Internet. Just think: we choose hosting based on ratings, making purchases in online stores (especially foreign ones) - we look at the reviews before reading the entries in blogs or social networks - pay attention to the number of “likes”, and there are also these types of ratings that contribute in the life of the user on the site of rivalry, for example, the same rating of habra people . We use them every day, without even noticing how firmly they entered our lives.
And what about the development of rating systems?
As a rule, a certain amount (or hours) is spent once on the development of rating systems for the site owner: the system is developed, implemented, and, in fact, works. It is rare when changes or additions are made to a working rating system, unless we are talking about really large projects.
Works - do not touch.
The network is full of ready-made plug-ins, libraries, and simple developments for rating systems, but the customer always needs something “original”, and speaking of code copyright, one way or another you’ll have to write with your own pens.
And what if on a site besides the usual rating of one or another entity, certain achievements or statuses are needed? In this case, in addition to an additional check for revision, a check for design and creativity will roll out, and the developer will have: facepalm :, because everything will have to be sawed. Or, you will have to develop a flexible system from scratch, and you should also write an admin for the whole thing! Naturally, everything should work quickly and be considered correctly, which means testing, optimization and refactoring will be added to the above points.
In this regard, we came up with the idea: why not bring all these calculations to the cloud? At the same time build a fairly flexible system, organize an API and implement it on projects. Some of the readers at this point will think: "who would doubt another startup." My answer is yes, this is a “regular” startup.
The name of the startup - Rangg - was formed from the phrase Rank Aggregation . Now the service is in development and “touch” it, unfortunately, habrazhiteli not work. We will definitely roll out the beta within a month, and the first to know about this will be Habr.
As you have already guessed, the essence of the project is to build a cloud service rating and achievements, which could be implemented with minimal effort on the project, enable developers and site owners to build their rating systems with achievements, ranks and statuses. We have compiled a short list of functionality that will be available at the launch of the project (can be changed):
- Essence rating (more than obvious)
- The assignment of "status" depending on the rating
- Uploading your own images of statuses and achievements (besides the standard ones that we will provide)
- JS notifications (for example, receiving some achievement)
- Statistics and activity log
At the moment, the RESTful API is being developed (not without the help of habr posts) and the service of providing access, configuration and statistics. The technologies we use on our project are quite popular: PHP + MySQL - service, NodeJS + MongoDB - API. The next article will tell about the project architecture and the integration of these fairly well-established bundles.
In conclusion, I would like to sincerely thank the administration for providing a blog; for your part, this is a huge step in support of startups.
Turning to the hacker readers, I want to ask for constructive criticism of the project idea.
PS If you made a mistake with the hubs - tell me exactly which article would fit better, correct it (I would like to add to “Analysis and design of systems - lacked karma).
Source: https://habr.com/ru/post/202566/
All Articles