feech

we waited 30+ years for Google to do the right thing and just start giving us an API to their search data.

oh and who cares if AI helped write something? Should I get all bent out of shape if you used a calculator to do some math today?

are you kidding? have you tried it? and no, not ai written so maybe those "clearly" glasses of yours need some cleaning

ChatGPT can answer anything, but first I have to pass a taxonomy exam. Did OpenAI ship its org chart as the UI?

Ok, so I read through those articles and my curiosity is peaked. If you had to guess, what would be your ETA on support for PWA's on IOS.. I think thats the elephant in the room.

I've been trying to stay away from Angular development. I've heard that ecosystem is just in a tizzy right now.

yea, cut me I bleed C# .. the transition to client libraries has been hard enough, but mobile has thrown me in a tizzy.

The straight up performance of Xamarin on my development machine was what through me. Getting it all setup and rolling and seeing the incredible amount of heavy lifting it took to get something rolling just turned me off completely.

I see what you mean about react-native, but from my perspective, the next-best-thing is a far enough second place finisher that I don't want to consider it. I still feel a native web based app running on all platforms is the ultimate best way to roll. We just need Apple to stop fighting it.

I completely agree on every point. Developers are such a creative bunch, I'm just surprised this has gone on so long. I went into this wary but hopeful that mobile dev had gotten to a good point, but I am just not seeing it.

I'd love to be able to just hook my editor up to a cloud environment that took care of all this for me :-)

To me, personally, its the trade off. A well built responsive HTML based UX is the easiest development approach. The thing that concerns me is that I don't know how much "easier" mobile dev can get, and I don't think it can come anywhere close to raw web based dev. So I concur :-)

Started reading those articles and immediately loved it. I did a bit of research a few weeks back because I had already been considering this approach. The consensus seemed to be that the app would suffer from performance issues primarily.

So, first off, I've never done mobile, but I've been writing software for 30 years. The biggest issues are probably obvious and are heard all over the place:

1) cross platform mobile-app development is a nightmare. I tried Xamarin and gave up because I felt like I would have to learn an whole new layer of syntax to do any UX work. Also the build times, the heavy lifting that was going to be required to setup the simulation environments, etc. just didn't make sense.

2) Setting up your development environment is just a complete nightmare. After a week or two of messing around, I finally got the Android emulators working at reasonable performance on my Windows machine. Still haven't even attempted to hook up a mac.

3) The amount of third party code, npm modules, and pre-processing required to build the simplest shell application is astounding. My current "shell" app, after first build, is 32k files and almost 300MB. Its absurd. and the app doesn't even do ANYTHING yet. The problem with all this code is that no one can possibly understand ALL this plumbing, and the instant something goes wrong, you're immediately sucked into non-productive rabbit holes.

All that being said, this is an awesome learning experience. I've been avoiding mobile development for years hoping it would mature, and I guess it has somewhat, but at this point, feeling like I won the lottery when I finally was able to set a breakpoint in my VS Code editor, run a react-native application through the emulator and hit the breakpoint. Ha!

This is a new app I am trying to launch. We had a ton of success with React as the web app, but building the mobile stuff has really slowed us down.