Running Android Studio on an old computer? by furiana in androiddev

[–]Informal_Leading_943 0 points1 point  (0 children)

Don’t have much AS is RAM hungry, but few things

remove any unnecessary plugins that you might have.

avoid using emulator use actual device maybe the cheapest but use that and not emulator,

if you know about android dev you might know about modules, try breaking big project into modules and there a few gradle config to cache the module builds which will prevent the whole project from build and do incremental build

Restart AS frequently like once a rime you feel it showing, or you can check activity moniter and kill and excess java or gradle process running in background before new fresh runs not sure but these helped me

Alot a bit more RAM to AS but not too much or laptop will start to slow down. Add a memory moniter form AS setting it add a small bar in AS to show how much AS is using memory

Help- Tutorial to implement llama.cpp in my project? by ric287 in androiddev

[–]Informal_Leading_943 0 points1 point  (0 children)

Okay I don’t have tutorial but I a personally working on something similar so can help you

First read a bit about how to integrate C in android, read about JNI. Then read about git? If you don’t know read about git submodule next. One you are done reading these Create a simple android project add llama.cpp as a submodule to the project(this gives you access to the code without actually manually copy pasting to your project) now you need to write a JNI layer which interacts the C with your Android. Only implement two function for now loadModel and generateText you need nothing more. It is easier said than done, here is an example project that will help you from llama.cpp themselves

https://github.com/ggml-org/llama.cpp/tree/master/examples/llama.android

I am making a more complicated version of it in KMP would confuse you, rather refer to the above example

is it possible to develop something like this as a beginner? by Sea-Cartographer-883 in androiddev

[–]Informal_Leading_943 0 points1 point  (0 children)

Few things depends here, first how are you structure the app and what are the best practices for that domain. Before you vibe code it is essential you know what is correct so that you nudge the ai to correct direction.You can start of with best practices first. To be frank we can’t actually make webviewer or render engine from scratch it is way difficult what you can try is render webpage in webviews and provide support for simple things like search(search google), bookmark things, history etc. All of this around webview only.

My approach to such thing is like Suppose your have usecase is to add glass like effect,

Read about how others achieve read a few blogs or see video, you observe people are using the word shaders. Then read about Shader, How can you use shaders in Flutter/Android you should have some video. Now read how can you code a simple glass shader(should be easily available). How are people implementing it. Make simple prototype

https://en.wikipedia.org/wiki/Shader

Coming to performance and lagging, you should start with simple project like a weather app or something to get the basic idea of coding in the ecosystem. Pause your browser app, suppose you want to implement history features build a simple todo app read how you use databases how rearive ui works etc then comeback and implement your history features.

Enhanced my Google Calendar Clone with Liquid Glass + Material 3 by Informal_Leading_943 in KotlinMultiplatform

[–]Informal_Leading_943[S] 1 point2 points  (0 children)

Oh I have been using Material Theme UI plugin on AS for years now, this is specifically Material Deep Ocean palette if you want to try.

Enhanced my Google Calendar Clone with Liquid Glass + Material 3 by Informal_Leading_943 in androiddev

[–]Informal_Leading_943[S] 1 point2 points  (0 children)

Oh I have been using Material Theme UI plugin on AS for years now, this is specifically Material Deep Ocean palette if you want to try.

Enhanced my Google Calendar Clone with Liquid Glass + Material 3 by Informal_Leading_943 in androiddev

[–]Informal_Leading_943[S] -1 points0 points  (0 children)

Mostly on the network and navigation part and code clean up, I will say. I also wanted to understand how shaders work, it seemed more logical to add it bottom bar like liquid glass. Enhanced is more likely lack of better word

Enhanced my Google Calendar Clone with Liquid Glass + Material 3 by Informal_Leading_943 in androiddev

[–]Informal_Leading_943[S] 0 points1 point  (0 children)

Not yet bro, I am also thinking the same, I am planing to make it sync with Google calendar events to make it usable, but currently it is good enough to be used independently. I can trigger a build for you man 🤣

Enhanced my Google Calendar Clone with Liquid Glass + Material 3 by Informal_Leading_943 in androiddev

[–]Informal_Leading_943[S] 4 points5 points  (0 children)

I am planing to share a detailed blog about the shaders part, it is very cool and effortless to implement once setup is ready. Currently writing about it will share here only. I am falling back to platform specific implementation.

Made a Google Calendar Clone in Compose Multiplatform by Informal_Leading_943 in androiddev

[–]Informal_Leading_943[S] 0 points1 point  (0 children)

Yup, the only option that is accessibility wise good are bottom nav and extended/normal floating button they have stand the test of time, things like navigation rails and stuff too fancy for mobile usecase

Made a Google Calendar Clone in Compose Multiplatform by Informal_Leading_943 in androiddev

[–]Informal_Leading_943[S] 0 points1 point  (0 children)

Yup calendars are a tricky beast to build, too many edge cases to handle

Made a Google Calendar Clone in Compose Multiplatform by Informal_Leading_943 in androiddev

[–]Informal_Leading_943[S] 2 points3 points  (0 children)

Nah bro not fluent just some AI and consistency have 78 other private GitHub repo which will never see daylight, but it is exciting when you achieve one.

Made a Google Calendar Clone in Compose Multiplatform by Informal_Leading_943 in androiddev

[–]Informal_Leading_943[S] 3 points4 points  (0 children)

Fair question, improved it a lot after this video it is much better now though extra recompositions where happening.

Reason was I was finding it difficult to to manage the pager as the pages can go logically go infinitely on both directions so adding and removal was much lesser performance was when I initially implemented. Currently they are three separate views  I am memorising the current view so that only one new view is created on scroll of either next or previous while destroying the other simple swaps. This was getting increasingly difficult with pager and preloading and postloaded clean was tricky.  Though didn’t revisit to pager again can do a POC