Why I built a dictionary app (wordnote.app)

Article summary

The author, a non-native English speaker, was reading a book and struggled with understanding certain words, leading them to search for a dictionary app that met their expectations. They found existing options lacking and decided to build their own app, prioritizing offline support, speed, and a noise-free experience. The author discusses the challenges they faced, including finding reliable data and navigating licensing models. The app is now available, and the author is open to contributions and feedback.

Main themes

• dictionary apps
• language learning
• offline support
• licensing models
• government funding
• technical challenges
• business models
• etymology and word derivations

What commenters say

• Some commenters suggest that the author's needs could have been met by existing features in iOS, such as the built-in dictionary and thesaurus.
• Others argue that dictionaries should be free and accessible, with some suggesting that governments could fund their creation and maintenance.
• There is disagreement over the best approach to funding and maintaining dictionaries, with some arguing that they are creative and curated works that should not be controlled by governments.
• Commenters also discuss the technical challenges of building a dictionary app, including finding reliable data sources and navigating licensing models.
• Some suggest that the app's requirements, such as offline support, are not trivial and require significant technical effort.
• There are differing opinions on the best business model for the app, with some suggesting that charging for the app itself could be a viable option.
• Others point out that there are existing resources, such as Wiktionary, that could be used to create a dictionary app.
• The importance of word derivations and etymology in a dictionary is also highlighted by some commenters.