ANDROID form fields save to db

Hello, and thank you for viewing my job. I have a fairly easy request, I'm looking for someone to create an activity that manages short text fields a user fills out then saves to their phone. Picture tapping a button and this would open a modal with a text field on top followed by a save/cancel button below. The user can enter a short one to three word entry into this text field and save it to the database on their phone along with a timestamp. I'd like there to be some way to "add another entry" prior to saving which would generate another line containing an identical text field below the first one etc... tapping "save" would save each individual line to its own unique entry in the database. They would need to be able to view/edit/delete the previously saved entries, so a simple way of displaying them and editing/deleting individually is required. Ordered alphabetically Lastly, I would be accessing this saved database info from another activity I've already built in my current app. I need to be able to send an intent from that activity (containing the "query" phrase a user is submitting) to see if there is a match in those saved database entries. If a match is found, we would let the initiating activity sending that intent know and provide it that saved timestamp data. Then we update the saved timestamp to the current time in the database for that entry and re-save the entry by overwriting. If an exact WORD or PHRASE match is found (meaning if a user is querying "walk my dog" and in the database we find an entry with the content matching exactly "Walk my DOG" it is considered a match - capitalization should be ignored! Another example, if someone were to query "cat" and there is a saved entry containing the text "caterpillar", this would NOT be a match. A third example, if they were to query "bird" and there exists an entry containing the text "a cute bird", this WOULD be a match and we would let the originating activity know the timestamp of this existing match. If ever a match is found we can stop searching, no need to continue looking. BONUS: While not required, If you can take the query being sent and perform whatever is the java equivalent of PHP's soundex() function so that if there is a typo in the query (or alternatively within the saved entry) and we find something that is a very close match via this soundex() equivalent, I would be willing to pay additional.