I’d rather just tweet a link to a blog post and let the discussion happen there. Plus, you get “free” eyeballs on it since it’ll appear in the commenter’s social graph.
If you wanted to “own” the data, you could periodically scrape the tweet’s comments.
I think there’s a cool product somewhere in there.
> Xcode 11.4 supports building and distributing macOS apps as a universal purchase. To distribute your macOS app as a universal purchase, specify the same bundle identifier as your iOS app in the Xcode template assistant when creating a new project. If you have an existing project, edit its bundle identifier in the Project Editor.
Thanks for your feedback. Honestly, I was just being sassy. It probably is like comparing apples to oranges. This technique does not concern itself with a cross-platform interface. It only makes it possible to keep the logic cross-platform so that the "only" difference is the UI implementation, which can be done using native SDKs.
One of the biggest reasons that I decided to distribute on the Mac App Store was to establish trust. If I embraced its limitations (i.e. sandboxing), it'd help me build a product that was more secure and have some sort of proof that it was.
Also, the company (me) behind the app is based in France, which has some of the toughest privacy laws. The privacy policy, although in English, is compliant with French law. The short version is that Emporter doesn't collect user data, or perhaps most importantly, user content.
I have quite a lot I want to discuss about this via the company blog, which ironically is part of the reason I decided to post a "Show HN". I wanted contextualize the product a little bit before inviting this kind of discussion.
Thanks for your suggestion! I was hoping to perhaps put together a short video to show it off in action (it really is quite simple).
That said, it might actually be easier for me to use the "accordion" approach, as you suggested, My video editing skills are pretty limited and this is currently a side project of mine that's completely bootstrapped.
Thanks for your feedback... why not indeed? I've updated it within product page (and In-App Purchases). It'll probably take a little bit for the description in the App Store to update, though.
Thanks for your feedback! I can definitely see why that's a deal breaker. Admittedly, I just thought people would be stoked that it was free to use and download it.
I have a few other things that I'm looking forward to sharing, though. I just started with this because it will hopefully contextualize some of the other content.
I was indeed trying to explain something technical (i.e. a tunneling service) in a non-technical way in an attempt to be friendly towards designers, but it seems like I still have some work to do on the product page.
If you wanted to “own” the data, you could periodically scrape the tweet’s comments.
I think there’s a cool product somewhere in there.