{'fraction_non_alphanumeric': 0.010706638115631691, 'fraction_numerical': 0.0, 'mean_word_length': 5.324324324324325, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Dealing with application complexity when designing for older users

Some simple approaches for reducing complexity within a prototype email system for older users are described. It is argued that these approaches, while successful, depend on limiting the richness of the interface and do not scale up to handling feature rich applications. Hence applications that suit older users may remain distinct from the fully featured applications needed by some younger users.