Putting ULAPI to Use
When we're playing with a new API, we ask: What interesting features could the API add to our products? How can this API make life better for our customers?
That's what this page is about. It contains a few starter ideas to help you think about what ULAPI can do for you and your customers. We're eager to hear your ideas, too, so please ask us questions and let us know what you're thinking.
Case Study 1: An image library with user-generated keywords
Imagine your application involves a database of images uploaded by your customers, who tag their own images with keywords so other people can search for them by concept. You might, for example, end up with many photographs of cattle in the snow, with keywords assigned like so:
|cows, snowing||cow, snow||vache, neige|
Problems: people use different forms of the same words as keywords (cow and cows, snow and snowing), and words for the same ideas in different languages (cow and vache, snow and neige).
Solution: use ULAPI's stemming and dictionary look-up features to support keyword search that can find the right images even though the form and language of the keywords vary.
Case Study 2: In-app dictionary
In a lot of apps, especially ones that are for reading or writing, it's handy for people to have quick access to a dictionary. Though there are built-in monolingual dictionary tools on some operating systems, there are seldom bilingual or multilingual dictionaries available.
Problem: Your customers need quick access to a (possibly multilingual) dictionary.
Solution: Use ULAPI's dictionary lookup and rendering tools, and any of its more than 30 dictionary datasets.
Here's an example of the iOS popup dictionary that we have available for licensing:
Need to add your own specialized vocabulary for lookup? We can work with you to build special datasets for just such a purpose.
Case Study 3: Word games
When we were doing play tests of our word association game Psychobabble, we discovered that people would often type one form of a word when the puzzle contained another form of the same word. In this game, penalizing people for typing cats when the puzzle contained cat was just frustrating, and made the game less fun.
Problem: How can we treat different forms of a word as identical for the purposes of the game?
Solution: Use ULAPI's pluralizer, singularizer, and alternate spelling detector to detect matches between words that should be considered the same.
The result? See here how our player has typed colour in the first image, and the game has granted the player a match with color in the second image.
And so on...
We have many more ideas of ways to put ULAPI to work. Text mining support, natural language database queries or game input, numbers written out in word form for a fancy countdown, help predict the next word in the user's sentence, etc., etc.
If you have language feature ideas for your apps and you want to know whether ULAPI can help you realize them, let's talk!.