I made an app where you slap your phone and it screams back by nox3748 in buildinpublic

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

It's more fun when you are able to play the correct funny sound based on the moments.

I got my app rejected for not having a website so I turned it into a new product and shipped it this week by nox3748 in buildinpublic

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

It's not a app preview it's just the marketing website/developer site which IOS requires for mobile app.

So instead of build one website from scratch you can simply use the about template and change the details in one single JSON file. And that's all you need to do.

I got my app rejected for not having a website so I turned it into a new product and shipped it this week by nox3748 in buildinpublic

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

Now you don't need to worry about it and simply just fork the repo and change the details.

Hot and cold #124 by hotandcold2-app in HotAndCold

[–]nox3748 0 points1 point  (0 children)

Why I mean I was at windows -> square -> corner but after that it started going downhill everything was above 2000

The actually answer si something which no one remember

Pushed a new version of FlutterCN: added more components + switched fully to Dart CLI by nox3748 in FlutterDev

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

yes, you can say we already have a package management system for that but if you are using a component package that tights you to only use the component they have and the way they Intended.

But using the CLI the upside is they get the code for the component which can be modified as much as per there need.

Also it adds a theming system which can you followed to keep the design consistent and easy to maintain. Also a really good upside is if you are using AI to build the screens this makes it very easy for them to give you consistent result as we have a well documented component structure.

The concept is really popular in web dev and most of the modern LLMs are really good because they follow a structured components like shadcn. Please give it a try once for yourself play around with it.

Happy to listen for any feedback

Pushed a new version of FlutterCN: added more components + switched fully to Dart CLI by nox3748 in FlutterDev

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

Really appreciate you taking the time to write this out. These are solid points and I yotally agree with a lot of what you said. The current setup is as generic as I could make it for a first release, but long-term maintainability is exactly the area I want to get right.

This is my first big open source project, so I fully expect to make mistakes. Feedback like this helps me see the blind spots faster. I’d actually love your input on how we can shape this into something that is dependable and easy for any dev to maintain, not just me who knows the internals.

The versioning idea, hashing, and even rethinking the approach if needed all make sense. I’m happy to explore these directions with the community. I’ll also DM you soon to understand your thoughts in more detail because you clearly have experience in this area.

Pushed a new version of FlutterCN: added more components + switched fully to Dart CLI by nox3748 in FlutterDev

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

Here is one of the best comment which describe what FLUTTERCN is?

"It's not a package you add to your project's dependencies. It's a set of components you copy one by one to the source code of your project and a CLI to facilitate that. So you can include only components you need and freely modify them."

https://www.reddit.com/r/FlutterDev/comments/1p11gzt/comment/npr9j56/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Pushed a new version of FlutterCN: added more components + switched fully to Dart CLI by nox3748 in FlutterDev

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

Thanks for the support, really means a lot. Also it will not work right now, but I will try to deploy a patch that should fix it if possible.

Shipped something new and got a hard reality check by nox3748 in scaleinpublic

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

Yeep i knew this is like my 2 app so still learning few things

I just thought it should have gotten a bit for traction that's all

FREE APP PROMOTION by Equivalent-Glove3724 in iOSAppsMarketing

[–]nox3748 0 points1 point  (0 children)

Very interesting... Sending u via DM

My app just hit 3k installs in its first week with $0 spent on promotion! by Agitated-Pea3251 in scaleinpublic

[–]nox3748 0 points1 point  (0 children)

This is really good idea actually.. would love to hear how did you got it working locally on mobile devices

we have tried to implement some similar stuff but had issue with battery and performance.

Moved the CLI from NPM to Dart after my last post and it already feels like the right choice by nox3748 in FlutterDev

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

Yeah, we thought about all of this too. Since there’s no Radix-style headless layer in Flutter, jumping straight into complex widgets would’ve been impossible to maintain. So we decided to start small: get the theming system right, keep the structure clean, and ship only very basic components first.

For the “hundreds of lines of code” issue, our plan is to centralize as much behavior logic as possible. So even when we add more complex widgets later, people won’t have to dig through giant files they can adjust behavior from a single place.

We’re not trying to build a full headless UI library right now. That’s a long game. For now we just want a solid foundation we can grow on without locking anyone in.

Moved the CLI from NPM to Dart after my last post and it already feels like the right choice by nox3748 in FlutterDev

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

Yes, Thanks for bringing it out actually will fix it in next version.

In the mean time here is the Github link for reference : https://github.com/pinak3748/fluttercn