TheEpikGamer211 wrote:

ilikescratch7169 wrote:

TheEpikGamer211 wrote:

ilikescratch7169 wrote:

ssvbxx wrote:

Bump

invalid bump from #11

valid.

why valid? someone responded then he bumped his topic in the SAME DAY

it appears for me it was yes terday.

you have to wait 24 since the last post to bump
13 and 17 is only a 5 hour difference

Mogus_man wrote:

TheEpikGamer211 wrote:

ilikescratch7169 wrote:

TheEpikGamer211 wrote:

ilikescratch7169 wrote:

ssvbxx wrote:

Bump

invalid bump from #11

valid.

why valid? someone responded then he bumped his topic in the SAME DAY

it appears for me it was yes terday.

you have to wait 24 since the last post to bump
13 and 17 is only a 5 hour difference

Not exactly true; if the topic goes off the front page, a bump is permitted even if 24 hours have not passed.

This post is getting very off-topic.

ssvbxx2 wrote:

That's just the block pallet, there's nowhere that you can actually drag your blocks.

k7e wrote:

ssvbxx2 wrote:

That's just the block pallet, there's nowhere that you can actually drag your blocks.

The block pallette is collapsible (maybe I should edit the OP to clarify that).

ssvbxx2 wrote:

p-p-p-p-p-p-p-p-p-p- wrote:

The editor was actually made mobile friendly 5 years ago, in 2023 - known as Scratch 3.0. It allows any device with the proper dimensions to run scratch without any issues.
The problem with phones in particular is that they have such skewed proportions. Technically, the entire site is mobile friendly, it's just that the site is too big for most phones. That's not an issue that Scratch can solve at this moment, but if you've tried using a bigger phone, it may work better on there.

That's what my proposal is trying to fix, to make the whole site as mobile-friendly as possible.

That is the point, it's not possible to be made more mobile friendly. The site can't tell what device you're on (only whether you're on mobile or PC, ipads counting in mobile), so they can't make 2 uis (one for mobile and one for ipads), and they can't make an app because that's rejected.

p-p-p-p-p-p-p-p-p-p- wrote:

ssvbxx2 wrote:

p-p-p-p-p-p-p-p-p-p- wrote:

The editor was actually made mobile friendly 5 years ago, in 2023 - known as Scratch 3.0. It allows any device with the proper dimensions to run scratch without any issues.
The problem with phones in particular is that they have such skewed proportions. Technically, the entire site is mobile friendly, it's just that the site is too big for most phones. That's not an issue that Scratch can solve at this moment, but if you've tried using a bigger phone, it may work better on there.

That's what my proposal is trying to fix, to make the whole site as mobile-friendly as possible.

That is the point, it's not possible to be made more mobile friendly. The site can't tell what device you're on (only whether you're on mobile or PC, ipads counting in mobile), so they can't make 2 uis (one for mobile and one for ipads), and they can't make an app because that's rejected.

You can always use media queries to modify a page to better fit a certain screen dimension. One of the most standard practices for responsive design which Scratch currently uses in their site code

Bump

I support this change, ex. list resising and variable limit changing. Actually, those parts should be made mobile-friendly first. Also, who uses IPhone to code? We really only need tablet support, which would probably be implemented first.

Catzcute4 wrote:

I support this change, ex. list resising and variable limit changing. Actually, those parts should be made mobile-friendly first. Also, who uses IPhone to code? We really only need tablet support, which would probably be implemented first.

Ipad support is already implemented, as already stated.

And you're right, nobody uses phones to code. I don't feel like this should be a high priority as it's such a niche feature that nobody would ever really use. Eventually, it might be cool, but it's a lot of work for a very, very small audience.

p-p-p-p-p-p-p-p-p-p- wrote:

And you're right, nobody uses phones to code. I don't feel like this should be a high priority as it's such a niche feature that nobody would ever really use. Eventually, it might be cool, but it's a lot of work for a very, very small audience.

Mobile support is practically a must on most websites, and if there is no mobile support for a site, users expect a mobile app. Scratch is meant to be very accessible, and mobile should at least be supported enough that users can look through a project on their phone. It may not seem like many people use Scratch for mobile, but there's ought to be a sizeable majority if you look around, given how many mobile internet users exist worldwide

ajskateboarder wrote:

p-p-p-p-p-p-p-p-p-p- wrote:

And you're right, nobody uses phones to code. I don't feel like this should be a high priority as it's such a niche feature that nobody would ever really use. Eventually, it might be cool, but it's a lot of work for a very, very small audience.

Mobile support is practically a must on most websites, and if there is no mobile support for a site, users expect a mobile app. Scratch is meant to be very accessible, and mobile should at least be supported enough that users can look through a project on their phone. It may not seem like many people use Scratch for mobile, but there's ought to be a sizeable majority if you look around, given how many mobile internet users exist worldwide

You are welcome to use scratch on mobile to do things like check notifications. But not only does almost nobody code on a cellphone, but the app store does not allow coding applications.

Catzcute4 wrote:

Also, who uses IPhone to code?

me

unmissable wrote:

Catzcute4 wrote:

Also, who uses IPhone to code?

me

Why. Literally why.

As good as of an idea this may be, unfortunately I think it's unlikely that the ST would create something like this, being that they struggle to add new (even tiny) features into Scratch as it is. If done correctly, a mobile editor could be a good idea, but the complications and problems that the mobile editor may introduce would likely be dramatic. The mockups show a possible/promising editor for mobile devices, but even these mockups would be a lot of work. Phone screens are tiny and even inputting text is sometimes difficult. I think that Scratch, a programming language that is inherently oversimplified and uses large blocks, would be extremely hard to consolidate into a small, mobile version. Not to mention that this would introduce problems regarding the limitations of mobile browsers, meaning this would likely have to be an app (not a problem for me but may be for some). I would focus on improving the mobile experience for running existing projects rather than editing new ones. The premise of your idea sounds great, but I'm not sure that the ST has adequate resources to create something of this scale. However, if provided with proper time and resources, this could (possibly) be a potential new feature in the future.

removed

ssvbxx2 wrote:

k7e wrote:

ssvbxx2 wrote:

That's just the block pallet, there's nowhere that you can actually drag your blocks.

The block pallette is collapsible (maybe I should edit the OP to clarify that).

There's still nowhere you could put the block, unless you can drag a block and collapse the block pallette at the same time.

MythosLore wrote:

ssvbxx2 wrote:

k7e wrote:

ssvbxx2 wrote:

That's just the block pallet, there's nowhere that you can actually drag your blocks.

The block pallette is collapsible (maybe I should edit the OP to clarify that).

There's still nowhere you could put the block, unless you can drag a block and collapse the block pallette at the same time.

That will also be there.

ssvbxx2 wrote:

MythosLore wrote:

ssvbxx2 wrote:

The block pallette is collapsible (maybe I should edit the OP to clarify that).

There's still nowhere you could put the block, unless you can drag a block and collapse the block pallette at the same time.

That will also be there.

How? It seems a difficult to implement something like that, especially in a web-native applicatoin.

(oops)