This creates Flutter's fundamental limitation: no code push capability. React Native developers can update JavaScript bundles at runtime through services like Microsoft's CodePush. Flutter's compiled Dart code is static machine code. There's no runtime interpreter in release builds. Once you publish an app, fixing bugs requires a full app store submission. That's typically 1-7 days for Apple review and hours to a... - Source: dev.to / 7 months ago

In my opinion it doesn't make any sense you can use https://microsoft.github.io/code-push/ which is free. I use this for my apps android/ios and works fine.. I hope it helps. Source: about 3 years ago

I come from smartphone app development and now moving to chrome extensions I miss something called CodePush which would push Javascript changes live to app store, but not native code so we could hot fix critical stuff without waiting for store reviews... Source: over 3 years ago

One feature I feel holding Flutter back compared to ReactNative and other options is Code Push. I really enjoy writing Flutter apps but the ability to push updates and bypass store reviews has been extremely valuable for multiple companies I've built apps for. https://microsoft.github.io/code-push/. - Source: Hacker News / over 4 years ago

Couldn't you just add the adults as testers to the Google Play app, avoiding oversight? The problem with breaking off from Google Play is you lose the ability to send push notifications. You could look at Code Push [0] for seamless updates. TBH its not the easiest to integrate with. [0] - https://microsoft.github.io/code-push/. - Source: Hacker News / over 4 years ago

If you build on the JVM and want to use Qdrant, the official client is io.qdrant:client — and it's built for Java. Every call returns a ListenableFuture, requests are assembled with protobuf builders, and it drags a gRPC/Netty stack onto your classpath. From Kotlin, that means fighting the language:. - Source: dev.to / 10 days ago

The stack runs on Qdrant for vector storage, Ollama for local embeddings, and optional Neo4j for a knowledge graph that I added later. I also set it up to route different operations to the best LLM for each task. It provides eleven tools for your Claude Code instance to manage long-term memory operations, and your memories data never leaves your machine. - Source: dev.to / 5 months ago

Qdrant: Open-source vector database optimized for hybrid search and easy integration with ML workflows. - Source: dev.to / 8 months ago

Yes, Java SDKs are critical. But you don't need to rebuild entire orchestration engines just to write agents in Java. The ecosystem already has platforms solving the hard problems: memory (Zep, Mem0, LangMem), tools (specialized platforms), vectors (Pinecone, Weaviate, Qdrant), observability (LangSmith, Helicone, Langfuse). Integrate, don't rebuild. - Source: dev.to / 9 months ago

James Allsopp adds, "LangChain or LlamaIndex for managing LLM workflows, especially if you're adding vector search or documents." These tools handle multi-step processes, essential for complex apps. - Source: dev.to / 12 months ago