This hits the core issue. AI can generate structure fast, but it doesn’t hold intent. So you get something that “works,” but doesn’t always align with why it exists or how it should evolve. That’s why the bottleneck shifts from building to guiding.

A repo is truly “ready” when anyone can clone it, run a few clear steps, and get the same result without guessing or fixing hidden issues.

This is a massive upgrade for Codename One The new iOS Modern and Material 3 themes look incredibly polished, and the attention to backwards compatibility is honestly impressive. The sticky headers, runtime palette overrides, and screenshot diff testing workflow are especially cool. Great to see the framework evolving visually while also improving performance and developer experience at the same time.

True — most AI app builders optimize for “safe and decent,” which is why many apps end up looking identical. The real difference comes from systems that prioritize design thinking and planning, not just code generation.

The only problem is that if the user anytime forgots the password and recovers the account the pgp key is reset and the time will show the account is newly created but in reality it was created many times ago

Nope! MCP is not ripe yet, changed transport from SSE to streamable HTTP in less than a year, and is just for LLM usage. This "protocol" is a subset of specific endpoints(OAuth, response schema, etc) and session persistence. Nothing you can't do with function-calling/structured output. Your question goes in another layer... Will users move to using LLMs as the primary way to interact with backend services? Actually, you're still designing REST for MCP... Integrations between systems will be deterministic, without MCP in the process, pure REST...