[ipqk]

I removed all my apps from the EU, and I will no longer publish any future apps there unless they become wildly successful in another country first.

My apps are tiny, free, and just not worth the hassle of figuring out what GDPR compliance is (even though they are likely GDPR compliant already since I don't store any info).

I think we're going to see a lot of small indie developers just not publish to the EU until it makes financial sense (which might be never). And that's exactly what happened here: Instapaper is a two-person team and they didn't have the time or resources to ensure compliance, so they just kept letting it slide.

I suspect we'll see much more of this to come for the EU.

[nine_k]

I don't see why the above is downvoted.

Yes, GDPR may be beneficial and all, but thinking that it does not have an associated cost of a higher barrier to entry is a bit myopic.

[Chilinot]

I would certainly recommend reading up on the GDPR legislation. There are plenty of summaries that are good and covers the important aspects. Because once you understand GDPR, complience can follow naturally while you develop your application. Even if you dont serve customers in EU, GDPR complience will benefit non EU residents as well, since you have then implemented tooling for proper management of private information.

And if your application doesn't store data, then it's a one time cost essentially. Which is the time spent reading up on the legislation.

[tzs]

> Because once you understand GDPR, complience can follow naturally while you develop your application

How do I naturally during development acquire an Article 27 representative?

[ipqk]

In addition, just noticed that Bonobos withdrew from the EEC due to GDPR

"Due to the new General Data Protection Regulation (GDPR), we're currently unable to offer products and services to customers in the European Economic Community. We apologize for the inconvenience."