word-view/WordView-android

AI Summary: Improve the user experience of the WordView language learning app by displaying a clearer, more user-friendly message when a network connection is unavailable. The current error message for `UnknownHostException` (no internet connection) needs to be replaced with a straightforward message like "No internet connection" in both the search and home sections of the app.

AI Summary: Implement a button in the application's topbar that displays the currently selected language's flag. The button should ideally also allow users to change the language by clicking it, triggering a language selection mechanism within the application.

AI Summary: The task is to fix a bug in the WordView language learning application where uppercase letters in song lyrics prevent correct word recognition and display as `IdentifiedWord`. The issue is that the application's word recognition system fails to properly handle uppercase letters, resulting in incorrect rendering of lyrics. The solution requires modifying the application's word recognition logic to correctly handle both uppercase and lowercase letters.

AI Summary: Trim the sound effects used in the WordView language learning app lessons. Currently, the effects are 5 seconds long with mostly silence; they need to be shortened to 1-2 seconds of relevant audio.

AI Summary: Translate the language options within the settings menu's strings.xml file to support multiple languages. This involves adapting the existing strings to accommodate different locales for the WordView language learning application.

AI Summary: Implement a local history system for the WordView language learning app. This feature will track the videos accessed by each user and display this history when the user clicks their profile picture. The history should be stored locally on the user's device and accessible through the app's user interface.

AI Summary: Fix a NullPointerException in the WordView language learning app that occurs when a user tries to open music without being logged in. The issue stems from a double negation (`!!`) in the JWT (JSON Web Token) check. The solution involves refining the JWT authentication logic to gracefully handle unauthenticated users attempting to access music content.