Introduction Designing a mobile app today goes far beyond building a beautiful interface. Native apps — whether for iOS or Android — need secure authentication, user role management, real-time communication with the backend, and scalable infrastructure to support growth. In this post, I’ll walk you through a clean and modern architecture to connect native mobile apps to a robust backend on AWS. The architecture is modular, scalable, and aligned with best practices for security and performance — without relying on overly complex tools. Why it matters: apps today are more than just UI A production-grade mobile app often includes: User login (email, Google, or others), Differentiated access for multiple roles (e.g., user vs admin), Secure token-based communication, A backend capable of handling business logic and data, Data storage, asset management, and scalable APIs, Compliance with Google Play and App Store requirements. All of these require a backend architecture ...
Last month I watch a video on YouTube about Google map maker.
It sounds cool contributing on something you know, and many people use. So I decide to start checking Google maps and find one mistake. I report it, at the beginning I though it was going to be reject it. But I was wrong, two days ago I received an email informing me that my suggestion was approved. So if you like Google maps and find some mistake you can edit it go ahead.
After this experience with google maps, I will give a try to OpenStreet
After this experience with google maps, I will give a try to OpenStreet
The biggest problem with contributing to Google maps is that you are essentially doing free work so that a company can wrap the free work you did in a proprietary license, make the source (the vector data) unavailable to anyone including yourself, and then profiting from it.
ResponderEliminarIt IS cool doing work on something millions of people will use, but doing free work for Google Maps just to so you can work on a widely used product would be like contributing to Microsoft Windows for free.
If map making interests you then I would strongly suggest going the OpenStreetMap path, which is also used be a very large number of people, but is free as in freedom, and is not work done just for the private interest of a for profit company.