Like anything, apps are just a bit shinier and a bit more popular when they're fresh and new. Just by virtue of the fact that yours is the new app that's available, you will get a good bump of downloads right at launch. This is exciting, and gives you hope that what you have is the next big thing. But the problem here is that being new is the reason that people are downloading your app, not necessarily that they know anything about what your app does.
While being new is the reason that an app will get downloaded, sucking is the reason why it will never get opened again. For many apps and startups with the attitude of getting to launch as soon as possible, people stop thinking about the consequences of pushing an app live that is fundamentally broken in some ways. Generally this means that after you get your bump of downloads, the vast majority of people will never open your app again, most likely deleting it.
This isn't as much of a problem when your startup is web-based, because you can react quickly to the pieces that are broken. When it comes to mobile apps though, the lag that is inherent due to the App Store review process means that you can't react fast enough. That is where Taplytics comes in. If you have Taplytics loaded into your app when you launch, you can react to the data you are getting extremely fast. You can make changes to the interface, design and flow of you app without needing to push an update. You can also hide the parts of your app that turn out to be broken, saving yourself from the inevitable bad reviews that can ruin a launch.
So if you're about to launch an app, just take some time to think ahead, whether that's by dropping in the Taplytics SDK or just having a plan for how to fix things quickly, because it can mean the difference between keeping your new users and losing them forever.