Hang on, this should be the number 1 point of your entire blog post. Honestly, if your post was titled the obvious "Don't make mobile apps only for one region" then you'd be getting a lot of comments saying "Well, obviously".
Seriously your problem here is not that you made a mobile app. Your problem is very clearly that you excluded 99% of your user base. Any chance you can explain the reasoning behind this..? I can't even begin to understand it. Outside of government required tax applications, I cannot think of a single successful single-region productivity app ever.
But I can assure you that regarding anything finance-wise, it's simply impossible to launch an app that that complies with local laws everywhere at the same time, especially without proper funding. Take Quickbooks, it exists for 5-10 years, and they're still postponing their launch in the French market. We've gone global since then, and we've grown in 10 weeks way faster than we did in 1 year.
Before that no one on earth will even care about your product enough to sue you.
On top of that it's quite expensive to go to France and sue you there as a foreigner.
These policies are reasonable and by following them you will rarely get into trouble in Western countries.
Of course some other country might object, then the app might be modified by me for this country or removed.
How many apps or website would exist today if checking every law everywhere would be the standard procedure? Probably around 100 websites and 25 apps in total would exist because only big corps can afford this.
Aside from that I don't understand what point you are trying to make here.
Are you suggesting that a developer should not release apps without first making sure that the app doesn't comply with any laws of any country?
And it's not something you casually forget to mention in your postmortem (ctrl+f for "France" and "French" in the original article).
You do a few manually, then put together scripts to automate each user with the correct sheet format, cover pages, currencies, categories, etc. by using the manual ones as a template.
Charge them a fee (maybe a flat fee for each report, say $40) and ask them if they'd like you to include that charge in the report from now on.
This is a tech solution for a services problem, imho.
Expecting someone to create and file their expense reports entirely on a phone is absurd. Most workers would prefer to do this kind of thing at a computer, being on a phone will simply slow you down: lack of a real keyboard, tiny screen, poor multitasking, etc. There's no reason to prefer a mobile app for this task over a desktop version.
Mobile productivity apps are generally best served as companions to existing web/desktop apps. Either to provide access to your data when you're not at a computer (not really relevant for this app), or to improve the workflow of something that would normally require a computer. For example, you might consider it a pain to have to save your receipts so you can later scan them into your computer and import them into your expense tool. A mobile app can improve this workflow by allowing you to immediately take a photo of the receipt when you get it, and having that receipt automatically synced into your expense tool.
Off the top of my head I can name two companies (Expensify and Shoeboxed) that provide this ability. That these guys dismissed their competitors as "heavy and complicated" seems to have missed the point.
Taking this experience and concluding that you shouldn't build a mobile app is simply throwing the baby out with the bathwater.
I was surprised there was no mention of Expensify - which I suspect is the business they were looking to disrupt - their UI is not awesome. BUT the UX is great. Take a picture of you receipt and done, email receipts handled, etc. but I use it mostly on desktop to submit reports - and use my mobile to take pictures of receipts.
Anyhow - your last line is a bit of a doozy. Are you suggesting that someone who wrote 2000 word post about their pivot to a better solution (this slack idea is great IMO) should just shut up because it might dissuade others from making the same mistakes he did? Based on your "counter examples" - I think he did the right thing. I hope OP keeps sharing his learnings - because it encourages me to keep trying different approaches. AND I'm going to install his slack bot for my whole company (giving them distribution). I hope you can hide under a rock so you don't get dissuaded from doing something. Sharing is caring, even if they failed.
The questions are right, the answers are wrong. The app did not (judging by the text, I never heard of it before) add the value they thought. Maybe it did not even work as well as they thought. Actually, I doubt that.
I won't argue too much into it, instead I will give you counterexamples:
1. I should be on the target audience, and I have never heard of the app before. 2. Concur seems to be doing really fine, working on the same problem - so they have either a better marketing or a better solution.
Bottomline: don't shy people away of doing anything because you failed.