Website and App -- 2

TK app TK app is an app we use to respond to user questions about their life situations. It could be your love life, financial, social and more and Kelly would advise you on your situation. The app After downloading the app, you would be presented with a sign in page. This could be a sign in from TK, using email and password or sign in with SM options. Then the user would get asked to stay singed in. if they do, sign in should persist. This helps the TK team with relevant data to help establish and grow the app. If the user stays signed in, we know the user would use us more frequently than a one-time sign in. Staying signed in also helps establish when the user is actively using the app and provide a faster service. One the user has decided on their sign in options. They would be welcomed by name and will be presented with the homepage. The homepage design is up to you as you would know the conventions of what the user would expect. This should have, to some degree some stories, even if they have to go to another part of the app to enjoy more. The app should have the following pages plus any you think would be a good fit to the app. Sign-in Homepage Settings Write to Kelly Favorites Story page While some pages could be on the app, they can be put onto specially set blog website to create a smaller app bundle. These include: About us Contact us Help Privacy policy/ Terms/ GDPR and governance While the app is being designed by you here are some additional pointers for page content Settings Font size/ font family/ hide images/ Write to Kelly Story title/ body/ review -> send with animation Favorites Save your favorite stories up to 10 with free and 100 with paid subscription Story page Story image(unless hidden) title, body and review in stars( no text input for reviews) and submit review. If they review story with 5 stars, they then get the option to add to favorites. The app as a business Users can use the TK app free of charge however if they do they will be presented with ads. Ads would be in full screen interstitial before the story is loaded. This is an important part of the model as users may be happy to use the app for free and view ads, so we have to make the most of ads. Again while you're in design and the finished app would be signed off by you, an idea is to have a few ad providers and have ads load as the user is selecting a story. I would suggest an on event listener so while the user is selecting a story an ad loads then then delay until a click listener of selecting a story. I would also suggest having more than one ads platform, choose the first platform and get confirm ad is loaded on delay, if no confirmation (token etc) then request the next platform to load add and seek confirmation. Then a third. Three should be enough however you can use this if no ad then call the next ad provider for more than three. Users can subscribe for currently $5/mo to stop viewing ads and to have the option to save more favorites. They would also have a rolling 30 day archive of previous stories rather than 30 stories in archive. \Benefits of subscription over free No ads 30 day archive 100 saved favorites