Both frontend and backend development come with their own challenges. However, I believe the industry has been grappling with unnecessary complexity for at least the past decade. Take React as an example: it's a library developed by Meta, which boasts a massive team of developers. But before tools like React, and even before Backbone, there wasn't a clear distinction between frontend and backend in web development.
This division is relatively new and, in many ways, has given rise to new challenges and job roles. Gone are the days when we were all considered full-stack developers, working seamlessly across layers of a web application. In reality, web development should be viewed holistically, even though there are multiple layers to it. The final product is singular and unified.
It's possible to simplify frontend development by selecting appropriate tools. For example, a combination of Rails with Hotwire and Stimulus, or similar setups in other frameworks, can make the process more straightforward.
This is happening in the driest desert in the world, this is a simpler but effective technique to get water out of the desert fog
https://youtu.be/w5cBSORuB6w?t=35
I've been following Esteban's project recently, I like the product very much it's really handy to give context on what we do on daily basis (coding in my case :D). Build in the open is the way to go, best of lucks to the watermelon team!
I think the Zendesk article forgot us, take a look at a truly open source solution for CRM with live chat, knowledge base, video calls, API integrations, product tours, newsletters and more. https://github.com/chaskiq/chaskiq
Thanks!. Yes, in Chaskiq you have conversations like Tickets. You can tag them and assign them to the right agent (manually or automatically). You can also create your own plugins to extend the features.
If you are looking for an integrated solution with many other features than only chat to build your support/sales/marketing pipeline take a look at https://github.com/chaskiq/chaskiq
And agree with you, being on development of a chat solution over the last two years I've realize that the AI sucks big time for chatbots no matter how hard we try they will never have the human touch. that's why I have avoided the NLP integration as much as I can. This lack of human touch is the reality of any chatbot that does NLP, sentiments analisis, etc.. they simply fail. I have tried xatkit and I could not establish a proper dialog either.
In that sense I've implemented in chaskiq some sort of path selector / decisional steps that you can compose for further routing assignment to human agents, and that works very well.
Very interesting project.
if you are looking for a 1:1 solution for video calls that you can embed on websites (to give support or to assist sales), take a look at https://github.com/chaskiq/chaskiq , it also has similar features found at Intercom or Drift
This division is relatively new and, in many ways, has given rise to new challenges and job roles. Gone are the days when we were all considered full-stack developers, working seamlessly across layers of a web application. In reality, web development should be viewed holistically, even though there are multiple layers to it. The final product is singular and unified.
It's possible to simplify frontend development by selecting appropriate tools. For example, a combination of Rails with Hotwire and Stimulus, or similar setups in other frameworks, can make the process more straightforward.