Check the acquisition promise
Read the store headline, screenshots and description. What problem is the app promising to solve?
Study the storefront ↗RealPage, Inc. · iOS
Explore the ad evidence, study the storefront, and build your next acquisition hypothesis.
01 / Creative research
Read the store headline, screenshots and description. What problem is the app promising to solve?
Study the storefront ↗Explore apps with direct store-link matches. Compare their hooks and formats without assuming the same approach works here.
Browse observed advertisers ↗Store rankings and revenue estimates describe market context. They do not establish ad spend, conversions or ROAS.
Review the market context ↗02 / Storefront & product
Study the product story and store experience behind the acquisition funnel.
03 / Market context
Keep revenue, downloads and store rankings separate from advertising performance.
The app sort of works, except being logged out when you re-open the app, occasionally showing a blank page and needing to be re-installed, and occasionally silently failing to sync until you log out and log back in, so you think you're seeing current tickets but you aren't. These are all pretty normal bugs, definitely fixable if given enough time, but they all come from the same place: this app is written with a sync-based architecture rather than a thin client (just displays a website rather than trying to write an app) or a partial update architecture (the way an app like this should work). This is an old problem, keeping a list of items synchronized between clients and a server, but it HAS been solved. An example of an app that uses a sync-based approach and does work is BeOrg, an app that handles the plain-text format "org-mode", which works similarly enough to a ticketing system that you should be able to get what I'm saying if you try it. As for what you should do now? Review your staff. Hire some EXPERIENCED programmers, put them in charge. Create a testing version of the application and a "live" version of the application. Make one team to fix bugs in the current version and another team to rewrite the app. Once the newer app reaches "feature parity" with the old app, rewrite your server to allow both to be used and release the new app in the apple "TestFlight" beta program, allowing people to use it if they want to and report bugs. Once you've tested the app that way, release it alongside the current app and slowly deprecate the old app. If you still need help after reading this, contact me and I will try my best to get you headed in the right direction.
I have tried to reinstall my app 3 times and it will not properly record time nor will it go to the close menu that allows me to properly close tickets. Also in the record function time jumps sporadically (jumps from 1 sec, to 3, then back to 1, etc). As of right now I can not close work orders
After this last update it seems to be running way better now. Thanks for stopping the inspection tab from loading 1st. Everything is still cluttered together. Would be nice to assign colors to specific tasks/work orders. And make readies are unorganized. Wish I could change the order in which they are listed. More customization would be nice. Need a notes area for internal maintenance use only. Also would be nice if I could see history of the unit without having to go to a desktop. I also wish I can change the categories in make readies by unit. Most of them are a waste of time for me. I really do like the time Recording though, that's a big help. All and all it's gotten much better but could be great.
OneSite Facilities Plus by RealPage makes property management simple and easy. Designed by RealPage, a leading provider of rental housing software,...