Gamification API Sample Clauses

Gamification API. The Gamification API will be the central entrance point for applications in order to access features with regard to gamification, individualisation and motivation. We want to emphasise that at this stage, the list of features is not final and will probably be enhanced when more and more features are added to PRECIOUS. • Amounts of Coins, Current Levels, Badges and Leaderboards Apps can always access the users’ current status in terms of Coins or Levels as well as accessing badges, trophies and the users’ place in Leaderboards and thus make in-app progress dependent on the users’ health status, which can of course also be improved via other apps. Thus, apps can generally contribute to progress in other apps if desired by the developer. • Transformation of Activities and in-app Tasks, Quests or Challenges into Rewards A metric will be defined translating measured activities and in-app progress into rewards contributing to the global reward system. Apps can access this information for instance to inform the user about potential progress in terms of rewards when a certain intervention is suggested to the user. Furthermore, as all users react differently to rewards, the moment when rewards are awarded can also vary across users. While some users expect rewards in a certain interval, others prefer unexpected and surprising rewards. This fact will be included within the API when potentially issuing Coins, as unexpected feedback has been found to increase intrinsic motivation (see Section 2.6). • Define progress Apps can have their own badges and trophies, which can be made dependent on aspects and factors decided by the developer. • Access friends & family If allowed by the user, developers can easily access settings and rewards of friends and family members in order to tailor their service. This can for instance be used to send and receive motivational messages from friends, family members or other linked contacts. • Create (Collaborative) Tasks & Quests Apps can have their own tasks and quests, which will be specified in form of interventions. There will be a standardised way to do this via the API, also when for instance creating social interaction with other users by making task goals etc. depending on other users. • Addressing the user Depending on the environmental context of the user, the Gamification API will provide the best way to currently address the user via different means, i.e. vibration, notification, sound. • Adaptive Aesthetics Apps can dynamica...
AutoNDA by SimpleDocs

Related to Gamification API

  • CLARIFICATION OF SPECIFICATION DOCUMENTS 4.1 Bidders shall promptly notify the Purchasing Agent of any ambiguity, inconsistency or error which they may discover upon examination of the specification documents.

  • Health plan specification The Employer will require health plans participating in the Group Insurance Program to develop and implement health promotion and health education programs for State employees and their dependents.

  • Core Profession Specific 3.1.1 Develop, implement and review communication strategies, tools and guidelines Profession-specific services, as listed in the National Board’s regulatory plan and annual budget.

  • Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • CERTIFICATION REGARDING DRUG-FREE WORKPLACE REQUIREMENTS The undersigned (authorized official signing for the contracting organization) certifies that the contractor will, or will continue to, provide a drug-free workplace in accordance with 45 CFR Part 76 by:

  • Training Delivery Type Code -- Code Short Description Long Description (If Applicable) 01 Traditional Classroom (no technology)

  • Training Designation Type Code Select and insert the appropriate training credit designation type code: Code Short Description Long Description (If Applicable) 01 Undergraduate Credit N/A 02 Graduate Credit N/A 03 Continuing Education Unit N/A 04 Post Graduate Credit N/A 05 N/A N/A

  • Interpretation & Application of Guidelines It is jointly agreed that the site representatives (union and management) are empowered to implement the guidelines as per the scope provided. It is jointly agreed that refresher training to explain the interpretation and application of the inclement weather clauses is to be conducted to ensure correct use. Unless these guidelines are followed, the employer will not be required to pay for lost time through inclement weather and the Disputes Board will be so briefed.

  • Classification Specifications The Employer agrees to supply the President of the Union or his/her designate with the classification specifications for those classifications in the Bargaining Unit.

Time is Money Join Law Insider Premium to draft better contracts faster.