FriendlyData VS Hammer.js

• Ease of Use
  FriendlyData allows users to interact with databases using natural language queries, which makes it accessible for non-technical users who are not familiar with complex database query languages.
• Time-Saving
  By enabling natural language processing, FriendlyData reduces the time it takes for users to get the information they need, facilitating quicker decision-making processes.
• Integration
  FriendlyData can be integrated with various platforms and services, making it versatile for different business needs.

Possible disadvantages

• Complex Queries Limitation
  While FriendlyData is useful for simple queries, it may struggle to accurately interpret and execute more complex queries, limiting its effectiveness for advanced data analysis.
• Language Ambiguity
  Natural language processing might not always accurately interpret user queries, especially if the input is ambiguous or lacks specificity.
• Dependency on Vendor
  Relying on third-party services like FriendlyData introduces dependency on the vendor for maintenance, updates, and support, which could pose risks if the service changes or is discontinued.

• Touch Gesture Support
  Hammer.js is specifically designed to handle touch gestures, making it easier to implement complex multi-touch interactions like swipes, pinches, and rotations without relying on native touch events.
• Lightweight
  The library is relatively small in size, which means it won't significantly increase the load time or bandwidth usage of web applications.
• Ease of Use
  Hammer.js provides a simple API that abstracts away the complexity of different input types, allowing developers to add gesture support with minimal setup and code.
• Cross-Platform Compatibility
  Hammer.js is designed to work consistently across various platforms and devices, ensuring that touch interactions behave similarly on different browsers and operating systems.

Possible disadvantages

• Limited to Gestures
  While Hammer.js excels at gesture recognition, it is not a comprehensive solution for all touch events, so developers might need to use additional libraries or custom code for other touch features.
• Performance Overheads
  In complex applications with many touch interactions, Hammer.js could introduce performance overhead, potentially leading to slower touch responses if not optimized properly.
• Maintenance and Updates
  Hammer.js is not as actively maintained as some other libraries, which could result in longer periods without updates or fixes for emerging issues and compatibility challenges.
• Dependence on jQuery (for some features)
  Some implementations or extended features of Hammer.js may require jQuery, which can be a disadvantage for projects that do not use jQuery or aim to minimize external dependencies.

Tracking FriendlyData since Mar 2021.

• Tattooing The Black Keys Fans Using MediaDevices and PixiJS

  Originally, I used HammerJS to allow the user to use their fingers to do this but I found it rather difficult to use two fingers and try to capture a photo of myself. It’s a bit easier to simply hold my phone firmly and use the sliders... - Source: dev.to / over 1 year ago

• Make Drag & Drop + DropZone with interact.js + reactjs

  Actually, I thought if I used hammerjs, it would be easy, but actually I gave up using that since it seemed that hammerjs's development wasn't active any more unfortunately. - Source: dev.to / almost 4 years ago

• Can i build this with wordpress plugin or editor?

  Looking at https://delassus.com/javascripts/app.js you can see they used hammer.js(https://hammerjs.github.io/) to achieve the gestures, which I am assuming is your focus here. Source: about 5 years ago

View more