Live data from Hacker News

Building a Cross-Platform Web and Mobile App from the Ground Up

ambrook.com

11–20 of 32 posts

Re: Building a Cross-Platform Web and Mobile App from the Ground Up

#11
post #5

Do farmers really use apps?

Of course, why wouldn't they use the latest stuff? Farming technology is literally the reason you and your (relatively) recent ancestors aren't slaving away in the fields. Doesn't matter if that's combine harvesters or logistics apps.

Re: Building a Cross-Platform Web and Mobile App from the Ground Up

#12

This talk at Nextjs Conf explores cross platform solutions for common issues like routing, styling and animation. Found it to be quite helpful! https://youtu.be/0lnbdRweJtA

Would also recommended this talk! It highlights some key libraries bridging these two (Next.js/ React Native) opinionated libraries together.

Re: Building a Cross-Platform Web and Mobile App from the Ground Up

#13
post #4

We do something similar across a React and a Next JS app. A little different because they are both web, but same principles of letting the clients do their own thing and having common backend logic. Also just started looking around your site. This is actually a quality engineering blog! We're actively implementing stylized components in a manner similar to yours.

Yes very similar, thanks for the reminder. So it’s four platforms in the end (Browser, Backend/Node, Android, iOS).

Re: Building a Cross-Platform Web and Mobile App from the Ground Up

#15
How is this “from the ground up”? It basically uses the same web technologies and back end from the existing web solutions.

Also, I missed the challenges of handling offline usage which was stated as a requirement, but the back end appears to be GraphQL queries to a server?

Re: Building a Cross-Platform Web and Mobile App from the Ground Up

#18
> the opportunity to approach the challenge of supporting multiple platforms without the constraints of legacy engineering decisions

While I am keen on this article, I must pause reading it to come here and plead that people say "prior" instead of "legacy".

Legacy - due to its provenance in Microsoft sales techniques to mean "not Microsoft" - implies "bad". When actually the decisions may have been good, at least at the time.

Post reply on HN