This document discusses using a Line access token in a Unity application. It shows code for a LiffController class that requests the token from an HTML page and stores it. The HTML page gets the token from session storage and passes it to the Unity app. Functions are also added to a library to close the Line window and request the token.
The document discusses guidelines for how companies should approach chatbots. It provides an overview of a development methodology for chatbots with 5 phases: 1) Introduction, 2) Requirements Definition, 3) Design, Development, and Testing, 4) Operation and Evaluation, 5) Development Methodology. For the Development Methodology section, it emphasizes the importance of an agile approach for chatbot development given the uncertainties involved. It provides tips to avoid potential issues with Scrum methodology in large enterprises.
This document discusses using a Line access token in a Unity application. It shows code for a LiffController class that requests the token from an HTML page and stores it. The HTML page gets the token from session storage and passes it to the Unity app. Functions are also added to a library to close the Line window and request the token.
The document discusses guidelines for how companies should approach chatbots. It provides an overview of a development methodology for chatbots with 5 phases: 1) Introduction, 2) Requirements Definition, 3) Design, Development, and Testing, 4) Operation and Evaluation, 5) Development Methodology. For the Development Methodology section, it emphasizes the importance of an agile approach for chatbot development given the uncertainties involved. It provides tips to avoid potential issues with Scrum methodology in large enterprises.
The document provides an overview of key aspects for developing practical and high-speed LINE bots. It defines "practical level" as having multiple functions, multi-turn dialogue scenarios, high throughput, and mechanisms for continuous improvement. "High-speed" is defined as focusing developer understanding and responsiveness rather than recreating features. The document discusses techniques for multi-skill bots using intent/entity extraction and routing, and for multi-turn dialogue using state management across turns. It also addresses issues that can arise and solutions like topic-based routing and state lifecycle management.
育てる is たのしい!毎日おしゃべりしたいLINEBOTの作り方
***
チャットボットはコア機能に絞り込むのがよいと言われるなか、”いもうとBOT”は10以上の機能を自然な会話の中に盛り込みました。その背景にあるねらいや仕組み、多機能を支えるアーキテクチャ、また、チャットボット開発そのもののエクスペリエンスなどについてお話したいと思います。
The document provides an overview of key aspects for developing practical and high-speed LINE bots. It defines "practical level" as having multiple functions, multi-turn dialogue scenarios, high throughput, and mechanisms for continuous improvement. "High-speed" is defined as focusing developer understanding and responsiveness rather than recreating features. The document discusses techniques for multi-skill bots using intent/entity extraction and routing, and for multi-turn dialogue using state management across turns. It also addresses issues that can arise and solutions like topic-based routing and state lifecycle management.
育てる is たのしい!毎日おしゃべりしたいLINEBOTの作り方
***
チャットボットはコア機能に絞り込むのがよいと言われるなか、”いもうとBOT”は10以上の機能を自然な会話の中に盛り込みました。その背景にあるねらいや仕組み、多機能を支えるアーキテクチャ、また、チャットボット開発そのもののエクスペリエンスなどについてお話したいと思います。