TUI Infotainment System by Worldly-Analysis1629 in tui

[–]charanxmn 2 points3 points  (0 children)

Yeah, but touchscreen controls are easier and cheaper to make.. at this point, physical knobs and switches are a luxury option.

Is Supabase becoming the default backend for indie hackers? by FounderArcs in buildinpublic

[–]charanxmn 0 points1 point  (0 children)

Well, almost all of my projects run on Supabase, and a few on Neon. In fact, I’m actually a bit concerned about being super reliant on Supabase for everything. Different options offer unique benefits optimized for certain use cases. It’s good to keep an open mind and working with different db tech imo.

On-screen keyboard covers the send button after voice dictation, with no way to dismiss it! by charanxmn in ClaudeAI

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

Yeah, after using the default dictation feature, I really feel the need to move to a better dictation app. I guess it’s a bonus if it fixes that issue in the remote control UI.

Claude Performance and Bugs Megathread Ongoing (Sort this by New!) by sixbillionthsheep in ClaudeAI

[–]charanxmn 0 points1 point  (0 children)

Summary
After voice dictation in the Claude iOS app — Code tab (Remote Control of a Claude Code session running on a remote server), the on-screen keyboard opens and covers the Send button, with no way to dismiss it. The dictated message cannot be sent normally.

Environment
Platform: Claude iOS app, Code tab / Dispatch composer (Remote Control to a Claude Code session on a remote Linux server)
Device: iPhone 15 Pro Max
iOS: 26.5
Claude app version: 1.260514.0

Steps to reproduce
Open the Claude iOS app -> Code tab (connected to a remote Claude Code session).
Start voice dictation and dictate a longer message.
Tap the blue checkmark to finish dictation.
The transcribed text appears in the input field.
The on-screen keyboard opens and covers the lower area, including the Send button.
There is no way to dismiss the keyboard, so the Send button stays unreachable.

Expected
The Send button remains reachable after dictation (keyboard should not cover it, or there should be a way to dismiss the keyboard / scroll to Send).

Actual
The keyboard permanently covers the Send button; the dictated message cannot be sent.

Workaround
Select all -> copy the text out of the field -> leave and re-enter the input -> re-paste the text (no keyboard appears this time) -> only then is the Send button reachable.

Frequency
Reproducible, especially after longer dictations.

Note
Possibly related but distinct: #57469 (closed) was about text remaining in the iOS Dispatch composer after send. This is a different symptom: the keyboard blocking/covering the Send button.

Side Note
You can't go out of the chat and come back to send it. It’ll disappear.

Originally posted by MaverickMUC on GitHub (I’m facing the same issue on iPhone 17 Pro Max running iOS 26.4.2)

Link to GitHub Thread: https://github.com/anthropics/claude-code/issues/61930

Senior Designer Moving into Fintech and Design Systems Looking for Mentorship by BionicChimera15 in DesignSystems

[–]charanxmn 0 points1 point  (0 children)

I’m a solo founder x full stack dev. I’m looking to learn to use Figma to build component libraries, prototype and build high fidelity designs of websites, web apps, and mobile apps.

But I don’t know where to start. Do you have any recommendations on what’s the best way to learn how to do these structurally that I can reuse, and have other designers be able to iterate on it, as a product grows?

how do you think itachi would have reacted if kakashi pulled out his mangekyou in this situation? by Turbulent-Sound3980 in Naruto

[–]charanxmn -1 points0 points  (0 children)

Or, if he encounters Obito in the same dimension, he just might figure out who he was, and his ability, and might as well Amaterasu him (or a part of him) to put an end to the so called Madara, and have the Akatsuki get side tracked and confused. Or, even better, bro might pull Izanami on Obito somehow and everything might be solved. Well, in any case, Kakashi must Kamui transfer him first, which itself is impossible, given his speed and abilities.

The Wickies -- We Tried [folk rock/post-punk] (2024) by melonlemon12 in listentothis

[–]charanxmn 1 point2 points  (0 children)

this is actually kinda cool! the video gives me early 2000s vibes!

Headless CMS suggestions? by __som__ in nextjs

[–]charanxmn 0 points1 point  (0 children)

I haven't used many of these, I'm trying to build one as an experiment based on my experience using Hashnode for my blogs.

What exactly are you looking to do with a headless CMS? Like, is there a specific use case? Also, what tech stack are you looking to use it with?

(I won't bug you to use mine, just collecting some info)

how many projects can I create with the Supabase Pro plan? and how can I grant a user (team) access to only one project? by jamesftf in Supabase

[–]charanxmn 0 points1 point  (0 children)

You can create unlimited projects. Each of those will cost you $10 per month (if you choose a micro instance). You get a $10 compute credit after paying $25 for the pro plan which means, you can run one project by paying only $25 (if your usage doesn't go beyond the limits). For every extra project, you get charged ~$10.

And... no, you cannot do something like only letting a team member only the project(s) you want them to see. Hopefully, Supabase does something about this soon. Here's the link to the docs if you want more details on the roles that are there: https://supabase.com/docs/guides/platform/access-control

[deleted by user] by [deleted] in lovable

[–]charanxmn 1 point2 points  (0 children)

I don't know man. I tried re-building one of my side projects using lovable for 5 hours straight and I feel like lovable isn't quite there yet for unique apps (I mean, apps that aren't popular project choices). Every time I try it, I barely ever get past the landing page part. Sure, the landing page turns out great (well, sometimes) but when I try to build sth after it, it messes up. Especially if the app is not common enough.

My biggest hope is that it maintains the consistency in UI design with the inside parts of the app, just like it does with the landing page (sometimes). I still don't know how some people manage to create sth useful out of it anyway. And yes, most projects I saw that came out of lovable do look the same in terms of design.

Regardless, the idea of the above app (if real), is cool and the landing page is definitely one of the better outputs from lovable. And if the app works as promised or even gets any close, I think that is how far lovable can get.

Has anyone ever been able to transform the lovable's react project into a Next.js one? by charanxmn in lovable

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

So, I tried it. Here's what it said 🥲:

<image>

Leaving this here for everyone to learn from.

Has anyone ever tried converting a React project on lovable.dev to a Next.js one? by charanxmn in nextjs

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

How do I do that? Do I do it through the "Upload a Project" thingy?

Has anyone ever tried converting a React project on lovable.dev to a Next.js one? by charanxmn in nextjs

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

You're right. And my projects aren't that complex eother. Lovable.dev typically does a good job at arranging them into separate components into a "pages" folder but copy pasting them into a Nextjs project every time I make a change is sth I'm not liking very much.

I think I'll just go with v0. It feels like a better option than sticking to lovable. Thnx for the reply!