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

Write code for the web

mrmr.io

Post reply on HN
Print view View original

351–360 of 364 posts

Re: Write code for the web

#351

Post by idle_zealot »

echelon wrote: post #192
idle_zealot wrote: post #111

Earlier quoted context omitted.

I'm not aware of any scare walls on iOS. On Android is a site is installable a little banner is supposed to pop up and ask if you want to install it. On iOS one has to open the site's share sheet and pick an install option nestled in there somewhere. I suppose that counts as a hoop, but how else would you surface the functionality without it being invasive and annoying for most users? I think a more pertinent problem…

Those are downloads though the app stores. The links merely funnel you though the stores. Native web downloads of apps are impossible on iPhone/iOS. You have to go through the app store. Native downloads of apks are possible on Android, but not until you navigate to the hidden settings and enable them. And even then, Google scares users from installing apps this way. Nobody in practice does this. It's effectively not…

> but not until you navigate to the hidden settings and enable them

This used to be the case for older Android versions, but isn't anymore. Currently any attempt to install an APK from an app without permission to do so will pop up a missing permission warning with a deep link into the relevant settings page with a switch you can flip. Flipping the switch will initiate the installation of the APK. I can't imagine sideloading being any easier without removing the permission barrier entirely, which seems ill-advised.

Re: Write code for the web

#352

Post by berkes »

DotaFan wrote: post #118
berkes wrote: post #104

Earlier quoted context omitted.

But a surprisingly large amount of apps don't need hardware functionalities or could easily provide (most of) their value without them. Sure, some high end games. But they're more an exception. What other app are you thinking of?

This is true, if it's basic app I'd certainly recommend web technology. But it's also true that clients many times don't know what they want and where they're heading. So, before we decide on tech, I do analyze with my clients what are their plans for the future with the app. It does pan out many of them would like to have notifications, storage, camera, offline..

notifications, storage, camera and offline are all supported by web-apps though.

Maybe not safari, IDK, but globally the most used browsers support this and have done so for many years.

Re: Write code for the web

#353

Post by morpheuskafka »

Quothling wrote: post #9

I once had to setup an Apple developer account to have one of our municipality apps shown as ours. I'm not sure why that was considering all our other apps never needed that, but it was what it was. It was a pretty terrible experience. First I needed an Apple account, and since I didn't really want to use my private one, I needed to create one for work. I couldn't create an "organisation account" so it was tied to me…

I believe governments and nonprofits are eligible to have the $99 Developer Program membership fee waived, not sure when this started but it is not super new.

Re: Write code for the web

#354

Post by gymbeaux »

spacedcowboy wrote: post #338
Drew_ wrote: post #299

Earlier quoted context omitted.

Objective-C is the only programming language that was genuinely unreadable on first glance to me so I would definitely agree that it's difficult to work with.

Personally i don’t see much difference between class obj = new class() and class obj = [class new] And i think the named parameters are easier to read And ARC gives you pretty easy memory management - basically “don’t even have to think about it” except for more-obscure cases, even then weak properties can help out. ObjC is really only a little more complex than C, but gives you so much more for that little increase.…

Your example isn't representative of an entire language, though. It's convenient to your case to use class instantiation, one of the easiest things to do in any language.

Re: Write code for the web

#355

Post by spacedcowboy »

gymbeaux wrote: post #354
spacedcowboy wrote: post #338

Earlier quoted context omitted.

Personally i don’t see much difference between class obj = new class() and class obj = [class new] And i think the named parameters are easier to read And ARC gives you pretty easy memory management - basically “don’t even have to think about it” except for more-obscure cases, even then weak properties can help out. ObjC is really only a little more complex than C, but gives you so much more for that little increase.…

Your example isn't representative of an entire language, though. It's convenient to your case to use class instantiation, one of the easiest things to do in any language.

Well, yes, I didn't put everything in the language into a post. You got me there.

How about generic containers that can store any object ? Even using the old syntax, it's pretty clear what's going on

NSMutableDictionary *container = [NSMutableDictionary new];

NSString * item = [NSString stringWithUTF8String:"hi there"];

[container setObject:item forKey:@"greeting"];

Where @"..." is a shorthand for a constant NSString

And then the next thing to add could be a number...

NSNumber * age = [NSNumber numberWithInt:18];

[container setObject:age forKey:@"age"];

Then add in an NSDate, or another NSDictionary, or NSArray type....

The standard library that comes with ObjC is really powerful, and since it's ubiquitous, it works really well across a range of apps.

And then there are some really nice design patterns. Create an NSNotificationCenter and enjoy the Observer pattern, tightly integrated into the event loop. Any object can notify any other simply by posting a notification, and any object can listen for them by registering interest. And since collections can store anything, it's easy to pass state around and make large applications work well without interdependency hell. Just one of the built-in nice things... And all without caring about memory management.

Re: Write code for the web

#356

Post by gofreddygo »

ahmedfromtunis wrote: post #15

Early on, I made the choice to not to invest in learning native mobile development. I focused all my limited time on the web, and I think that, for once, I made the right choice. Today, one can build amazing stuff for the browser. And, in my very humble opinion, the vast majority of apps should've been WebApps — except for maybe Uber, Google Drive, and games. I worked in the journalism business, and, in my country, t…

This comment almost reads like from another dimension. I made the choice to stick to web too.

But everywhere I look, IOS, mac, android, windows on the phone, tablet, tv, cars its all apps. Be it under the guise of security, features or whatever, all of the UI is driven from apps. Some do a better job than others, but sucky or not you're forced to go the app route.

Re: Write code for the web

#357

Post by magic123_ »

lcnPylGDnU4H9OF wrote: post #219
Rohansi wrote: post #181

Earlier quoted context omitted.

Unfortunately for mobile games iOS tends to be where the majority of the money is.

Where are all the good iOS games? I don’t know if I’d be able to name more than a handful[0]. How many people are making -- and similarly monetizing: upfront cost sans micro-transactions -- things like Mindustry? 0: Mindustry https://apps.apple.com/us/app/mindustry/id1385258906 and two more which are available with an Apple Arcade subscription, maybe also for individual purchase: Dandara https://apps.apple.com/us/app…

This was shared on HN a couple months back, I found some nice games there: https://nobsgames.stavros.io/

Re: Write code for the web

#358

Post by depressedpanda »

no_wizard wrote: post #349
depressedpanda wrote: post #321

Earlier quoted context omitted.

You're speaking like Apple will get away with their malicious compliance and petulant behavior. I'm not so sure they will, now that the cat is (finally!) out of the bag.

I'm not as hopeful that globally Apple will face regulatory scrutiny as much as it has in the EU, and even then, the EU only goes so far as well. They have as of yet had nothing to say about Apple's solution to their regulations around this

True.

However, if the EU is silent because it considers Apple's reaction acceptable, the new laws are meaningless, unnecessary, a total waste of time, and an embarrassment to the EU.

So my hope is that they realize this and the silence is due to the EU preparing to put Apple in its place.

Re: Write code for the web

#359

Post by gymbeaux »

spacedcowboy wrote: post #355
gymbeaux wrote: post #354

Earlier quoted context omitted.

Your example isn't representative of an entire language, though. It's convenient to your case to use class instantiation, one of the easiest things to do in any language.

Well, yes, I didn't put everything in the language into a post. You got me there. How about generic containers that can store any object ? Even using the old syntax, it's pretty clear what's going on NSMutableDictionary *container = [NSMutableDictionary new]; NSString * item = [NSString stringWithUTF8String:"hi there"]; [container setObject:item forKey:@"greeting"]; Where @"..." is a shorthand for a constant NSString…

I think you’re making my case for me. All of that seems easy and straightforward to you, but not to me. It’s worth noting that I struggle similarly with C++ and Rust. I just think the syntax is harder to read than a Java or a C# or a Python.

Re: Write code for the web

#360

Post by spacedcowboy »

gymbeaux wrote: post #359
spacedcowboy wrote: post #355

Earlier quoted context omitted.

Well, yes, I didn't put everything in the language into a post. You got me there. How about generic containers that can store any object ? Even using the old syntax, it's pretty clear what's going on NSMutableDictionary *container = [NSMutableDictionary new]; NSString * item = [NSString stringWithUTF8String:"hi there"]; [container setObject:item forKey:@"greeting"]; Where @"..." is a shorthand for a constant NSString…

I think you’re making my case for me. All of that seems easy and straightforward to you, but not to me. It’s worth noting that I struggle similarly with C++ and Rust. I just think the syntax is harder to read than a Java or a C# or a Python.

Jeez, Java is a nightmare! And I’m not a fan of Python either. I think we’ll just have to agree to differ…
Post reply on HN