Yes, building your own app can work well if it solves specific frustrations like manual card creation and forced paths. Your app with a built-in dictionary and one-tap saving is a smart way to streamline vocabulary capture and review. However, its long-term value depends on how well the spaced repetition algorithm is implemented and whether you maintain the app over time.
Many learners face the same problem: paper notebooks are hard to revise, paid apps lock features behind subscriptions, and Anki requires upfront effort to create cards. Your approach addresses these by combining a dictionary lookup with immediate saving and spaced repetition. This reduces friction, which is key for consistency. The tradeoff is that building and maintaining your own app takes technical skill and time that could be spent on other aspects of learning, like speaking or listening practice. Also, without a large user base, the app may lack community support or regular updates.
For practical next steps, first ensure your spaced repetition algorithm follows established principles (like the SM-2 algorithm or similar) to optimize retention. Test it against a simple paper-and-phone system: use a free flashcard app like Anki for a month and compare your recall rate. If your app performs similarly or better, it's a keeper. Second, share the app with other learners for feedback, especially on the dictionary accuracy and card design. Third, consider adding features like example sentences from real Dutch media or integration with reading tools to make it more comprehensive.
Honest tradeoffs: Your app is free and tailored to your needs, but it lacks the polish and community decks of Anki. Anki has decades of research behind its algorithm and thousands of shared decks, but its learning curve is steeper. A paper notebook is low-tech but slow for review. Your app sits in between, offering convenience without cost. The biggest risk is that you might stop updating it, which could lead to bugs or outdated content. If you enjoy coding, this is a great project; if not, it might become a distraction.
Concrete next steps: (1) Benchmark your app's recall rate against Anki for 100 words over 30 days. (2) Get a few fellow learners to test it and report bugs. (3) Decide if you want to release it publicly or keep it personal. Either way, document your approach so others can learn from it.