Thanks for sharing your experience. I can relate to many of the struggles you are facing with Just Landed. My app StockSwipe shares similar struggles as the finance space is a hard one to crack. StockSwipe uses several data sources including finance APIs, backend database, remote server and a few third party libraries. Here are some of my issues I faced:

Launching a remote server

My first app Chronic Timer was started with almost no coding experience so my experience there definitely helped me when I started working on StockSwipe. StockSwipe was my second app and its development overlapped with Chronic Timer. As Chronic matured, I shifted my focus towards StockSwipe, all while still learning Swift and more advanced coding concepts etc. On top of that StockSwipe required a remote server so I can present users with professional looking chart cards and allowing to me host a charting library. This experience was an extension on top of app development and brought on alot issues that I needed to iron out, including the knowledge to execute this part.

Then that server got hacked

I got everything setup — my server was running — my app was in production — charts were being loaded as expected. One month after this success my server got hacked. I PANICKED!!! The app was in production and most of its functionality relied heavily on the server. The hack was a result of my inexperience in that area. I was not a UNIX guru nor had I ever setup a server. So during the setup process, I fiddled around with alot of packages and folder rights changes etc and ultimately exposed insecurities in my setup. The panick forced me to do a 8-hour marathon to fix the issue and I spent the next several days beefing up my server security as I learnt more on the topic.

Parse 1-year shutdown countdown

Guess what? my backend database is Parse. As with 90% of new developers, Parse is the go to backend database. The simplicity, community and API make it really idea. Even with its small problems and shortfalls, the platform is amazing.

Both Parse and Yahoo YQL outages

Happened already several times, including today!!! As I write this, if the production version of StockSwipe (on the App Store) actually crashes on launch. Thats what happens when both Parse and Yahoo have outages and your app gets exposure to these edge-cases. Yesterday I frantically tried to patch the app and push out an update, which is right now in review by Apple.

The more datasources, the more intersections points

All the above are really intersection points, areas of friction that could result in outage, crash or simply inconvenience. StockSwipe depends on these and makes calls to them all the time. If I look at Chronic which almost has not intersections, the crash rate is significantly higher. That makes sense of course! Taping into all these points has its risk

Only time will tell

Like in your case, I think its only a matter of time until I run into an issue that breaks my app indefinitely. Not to mention I feel I have reached my technical potential in this area and feel that I can only take it to the next level with the help of a team and with financial backing.

Ultimately I understand your decision because at the end of the day it comes down to making a great product. If the issues outweigh the potential benefits and growth potential, it makes sense to wind down and gracefully say goodbye.