Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Leaving the Mac App Store

blog.sketchapp.com

Post reply on HN
Print view View original

321–330 of 424 posts

Re: Leaving the Mac App Store

#321

Post by odbol »

ThomPete wrote: post #199
pietro wrote: post #179

Earlier quoted context omitted.

How is Paddle working for you?

Surprisingly good. They don't support anything out of the box but they always seem to have a workaround (for instance I am switching to a "nag" demo model instead of a time based one i.e. like Sublime) Stuff like that is not natively supported by Paddle but it will be and there are ways to do it through their framework. And as long as I price my app at around $10 or more it's cheaper than MAS. I am writing a "year in…

I'd love to read that post... what's your blog?

Re: Leaving the Mac App Store

#322

Post by ThomPete »

odbol wrote: post #321
ThomPete wrote: post #199

Earlier quoted context omitted.

Surprisingly good. They don't support anything out of the box but they always seem to have a workaround (for instance I am switching to a "nag" demo model instead of a time based one i.e. like Sublime) Stuff like that is not natively supported by Paddle but it will be and there are ways to do it through their framework. And as long as I price my app at around $10 or more it's cheaper than MAS. I am writing a "year in…

I'd love to read that post... what's your blog?

http://www.ghostnoteapp.com/blog/2015/03/ although I am probably also going to put it on my personal blog http://www.000fff.org.

Re: Leaving the Mac App Store

#323

Post by kybernetyk »

pietro wrote: post #179
ThomPete wrote: post #52

I used to have an app in the MAS but recently removed it and is using Paddle instead. There are so many things wrong with the MAS. Sandbox is the biggest complaint I have. I can understand it with the iOS to some degree. At least there they are constantly providing new features and hardware changes to help apps keep being innovative. To give an example of the Sandbox issue. We are using AppleScript for some of our lo…

How is Paddle working for you?

I tried them. Integrating their SDK is a breeze. 30 minutes and you're ready to go. I also signed up for their paid analytics package. It's OK - nothing revolutionary but enough to track events.

A few weeks later I wanted to cancel the subscription (app development would take a little longer). But there's no button to cancel. So I wrote them an email and all I got was a reply where they'd like to give me a Skype call to "talk over my decision".

That and their regular "customer engagement" emails (I just want to use your service, I don't want to video chat every weekend) made me choose Devmate instead.

(I still pay the $10/month for the analytics so I guess their plan worked).

Re: Leaving the Mac App Store

#324

Post by profmonocle »

optimuspaul wrote: post #94

I pretty much only use the Mac App Store anymore. There are maybe 2 apps I use that I get outside of it. I have a bunch that I are woefully out of date because their developers abandoned me. It's too bad that rather than trying to push to make it a better place developers are just leaving.

Developers have been sending feedback to Apple for many years, and they haven't listened. The only option left is to vote with their feet.

Look on the bright side - losing big-name apps might finally force Apple to fix the MAS, then those devs might come back.

Re: Leaving the Mac App Store

#325

Post by odbol »

mrschwabe wrote: post #70
greggarious wrote: post #49

Earlier quoted context omitted.

I would switch if I could find a good open source RAW image editor to rival Photoshop.

The latest Photoshop on Linux is quite attainable; I have CC running smoothly via VMWare Worksation 12 / Windows 7 (new versions of VMWare have DirectX/OpenGL and let you allocate GPU memory) ... but unfortunately that combines 2 proprietary solutions so guess it doesn't exactly fit your criteria.

So "Photoshop on Linux" means "Photoshop on Windows on Linux"... that's not really a solution. That's Windows.

Re: Leaving the Mac App Store

#326

Post by api »

microtonal wrote: post #167
ThomPete wrote: post #52

I used to have an app in the MAS but recently removed it and is using Paddle instead. There are so many things wrong with the MAS. Sandbox is the biggest complaint I have. I can understand it with the iOS to some degree. At least there they are constantly providing new features and hardware changes to help apps keep being innovative. To give an example of the Sandbox issue. We are using AppleScript for some of our lo…

Although I am happy that apps are moving out of the MAS (it is slow, updates are slow, no possibility to offer upgrade licenses), as a user, Sandboxing is something that I want for every possible application. The model where an app can e.g. touch your whole home directory should go.

Agreed, but it should be something you can change or opt out of if it is needed.

There's a difference between limiting and requiring approval for a dangerous but often useful activity and outlawing it entirely.

Re: Leaving the Mac App Store

#327

Post by krschultz »

nailer wrote: post #281
rimantas wrote: post #257

Earlier quoted context omitted.

xml/json as uses now is data transfer format, not some UI markup. As for why would it be better — because Cocoa is light years ahead in UI libraries and optimizations compared to web mess.

The app store has never felt slower than native apps for me. Instagram also seems to do pretty well.

Instagram is a native app.

Re: Leaving the Mac App Store

#328

Post by jonknee »

s73v3r wrote: post #247
jonknee wrote: post #152

Earlier quoted context omitted.

Steam has done well with that model for games, but being Mac only would be a tough sell. Apple's big advantage was instantly getting the App Store on every Mac.

Who says they have to be Mac only? It'd probably work out better to be on all major platforms, that way you can sell the feature of buy once, run on all platforms the software runs on. You also could allow single platform things onto your store too, like Sketch.

Because the vast vast vast majority of apps aren't cross platform?

Re: Leaving the Mac App Store

#329

Post by ThomPete »

kybernetyk wrote: post #323
pietro wrote: post #179

Earlier quoted context omitted.

How is Paddle working for you?

I tried them. Integrating their SDK is a breeze. 30 minutes and you're ready to go. I also signed up for their paid analytics package. It's OK - nothing revolutionary but enough to track events. A few weeks later I wanted to cancel the subscription (app development would take a little longer). But there's no button to cancel. So I wrote them an email and all I got was a reply where they'd like to give me a Skype call…

Looks interesting. Why did you change?

I am working on another product too so I am always looking for new opportunties.

Re: Leaving the Mac App Store

#330

Post by simonh »

pcwalton wrote: post #148
simonh wrote: post #97

Earlier quoted context omitted.

I'm not sure who you're quoting with those quote marks. It's not Apple though, because I don't believe they ever said any such thing. The reason Apple has always given is security. This is the reason they gave for not allowing third party access to the JIT version of the javascript engine. Their critics at the time claimed this was really because they didn't want other browsers competing with Safari, and they'd never…

> The reason Apple has always given is security. This is the reason they gave for not allowing third party access to the JIT version of the javascript engine. This doesn't make sense. You could disable the JIT, compile WebKit to native code, and ship it on iOS without the app requiring any more technical permissions. Apple just doesn't want you to do that for business reasons. If you want to maintain that it's a secu…

Your comment doesn't make sense. You've always been able to embed the renderer with non-JIT JavaScript. Now you can build an app with full JIT embedded, so saying they don't want you to for business reasons is obviously false. They do let you do it.

The attack vector they're concerned about is to do with the JIT exposing access to shared memory. As for alternate engines, any such engine would need to include a JavaScript engine, which immediately opens up vectors for attack. That's why the ability to download and execute code is restricted. now, thanks to a robust and secure cross process communications framework, many restrictions that were supposedly 'for business reasons' have been lifted.

Post reply on HN