PyraEthan12 wrote:
scratchusername40 wrote:
supersonic61223 wrote:
(#390)
scratchusername40 wrote:
I am an iOS developer, Apple enthusiast, and web developer so I feel like I am qualified to comment on this.
First of all, the App Store guidelines do not block Scratch from making an iOS/iPadOS app. That was changed a while ago, and you can find all sorts of apps that allow coding in much more powerful languages.
And, they literally have the ScratchJr app which came out after the Scratch Viewer app was removed from the store. So the entire debate is literally null.

As for the development needed, there are several options you could take. Scratch runs as a React web app right now. React has a variant called React Native which is used for native development. It's not easy to transfer from React to RN, but it's definitely not starting from zero. There's also Cordova which, while probably not ideal, will build a native app directly from the current codebase in a few minutes. Finally, they could start from scratch (pun intended) and build a native Swift and SwiftUI app, which would be massive ordeal. The Scratch Team would probably use React Native if I had to guess.

There's no real reason why they haven't done this already other than it's not their priority. The ST could easily do this if they wanted. They probably want to do it. It just isn't a priority for them.
(Also, Scratch Team, if you're reading this, I will contribute to a native SwiftUI app if you make one!)
Read this I beg of you this is so annoying to look at just read this and get over it. The Scratch Team could make an iOS/iPadOS app at almost any time they wanted, they just need the time to do so which I'm pretty sure they do considering they can update Scratch to remove exploits in enough time where little to no one is affected.
Yeah, this thread is kind of going in circles. There's no technical or legal reason why they can't do it, they just haven't gotten around to it.
I personally think ST just doesn’t care, as Scratch is also available on the Mac App Store, plus it would be too much effort regarding how the website works just fine.

This could be true, if the website DID work fine. (It doesn't.) The website has multiple issues on mobile devices, such as worse performance and broken hitboxes for the UI. There is also no support for multitouch which could be included with all versions of the client if they made a iOS oriented client.