4 ms·
I do a lot of flutter development and I never really have understood widget makers like this because they always end up falling flat on edge cases. Does it real
by latchkey 7y ago
I do a lot of flutter development and I never really have understood widget makers like this because they always end up falling flat on edge cases. Does it really speed up development time to drag/drop some boxes around? Doing this is already just a few lines of code in flutter and the hot reload is pretty amazing fast.
- nexuist 7y agoYou are approaching this from a developer's perspective, which is fine, but you fail to consider other skillsets. For example, if I have a team with designers, they likely know their way around Sketch and Figma and onboarding them onto something like this wouldn't be too difficult. At this point they can start contributing real, demonstrative code that compiles out of the box. Sure it lacks actual functionality and maybe it's a little rough around the edges, but that's not the point. The point is that I, as one of the few developers on the team (or maybe even the only one) have a greatly reduced workload because now everyone can contribute to building the UI. With frontend out of the way, I can work on backend functionality exclusively and marry the two later on. From the year that I've worked with Flutter, the framework makes it easy to separate those two which further adds to the efficiency gains. Rough edges can be cleaned up relatively easily and the time sunk into cleanup probably adds up to less time than starting from scratch. As a real world example, I have been building a mobile app for my startup since this summer. My girlfriend, who wanted to get into UI/UX design, is learning the ropes with the material widgets and making demo UIs by herself. With a few more weeks of practice, she will be equipped to start building some of the views in my app without further guidance. This takes a huge load off of my shoulders, and it's really where Flutter shines.
- latchkey 7y agoI am thinking from the perspective of a user of a product like this. I personally do both development and design work. Your example does not convince me that it would save time ('probably' isn't enough) or be generally useful enough that a designer could be convinced to drop Sketch for it. As a designer, I want to use Sketch. As a developer, I want a Sketch design over generated code. For sure, it is a neat experiment to create something like this, but time and time again, people always resort back to tools like Sketch. I think this developer would be better off spending their time building out a super epic component widget library than trying to build a visual designer.
- nexuist 7y ago>For sure, it is a neat experiment to create something like this, but time and time again, people always resort back to tools like Sketch The difference this time around is that the visual designer language...is the real development language. I've also tried using these visual designers before. They all seemed half assed and had glaring limitations. This one may end up being no exception. But I think, combined with Flutter, there may be something gold here. The key being that this visual editor is really a glorified text editor rather than a glorified art program. Sketch, for example, outputs PNGs at the end of the day. You can't throw those into your app and call it production ready. This "widget maker" outputs dart files. That's real, executable code. If the overhead visual designer is flexible enough, the only walls you may end up hitting are the ones set up by the widget implementations themselves. At that point you'd have to deal with those walls manually anyways, so you haven't lost any time really. One of my fever dreams over the summer was to build a voice controlled Flutter widget builder, such that I could sit in front of my TV and simply transcribe a UI from my head directly into the emulator. OP's project is a good first step towards that goal. Just imagine: "Give me a scaffold with a column layout..." "Add a raised button to this container's body" "Set its color to sky blue" "Show me this widget's properties" "Make this a stateless widget called SpecialButtonBar and have it take three arguments..." Again, it doesn't have to do all of it. But having written code to play with is a much better starting point than having nothing. Flutter's composability means that there aren't many different approaches you or a machine can take to arrive at the same result - you will end up with very similar widget trees which means this is a task ripe for automation.
- latchkey 7y ago> The difference this time around is that the visual designer language...is the real development language. Really? What is this then... https://reactstudio.com/ https://reactstudio.com/ ... (just one of many many examples). > The rest... I admire your ability to dream. =)
- Const-me 7y ago> the visual designer language... is the real development language. Microsoft tried that before. Designers prefer Adobe tools. https://docs.microsoft.com/en-us/visualstudio/xaml-tools/creating-a-ui-by-using-blend-for-visual-studio?view=vs-2019 https://docs.microsoft.com/en-us/visualstudio/xaml-tools/cre...
- MAMAMassakali 7y agoHow has been your experience with flutter? Are you a native developer? How does it compare?
- latchkey 7y agoI'm pretty happy with it. I haven't done any android or ios dev, but I did build an app on the danger hiptop a very long time ago! i've done a huge amount of web front/back for a long time. I picked up Flutter to feel pretty solid on it, on my own, in about 2-3 weeks of effort. It really depends on the application though. In my case, I wanted both android and ios. Building for both platforms is pretty easy (once you setup all the keys and such). I also quite like the material-ui components... especially for something greenfield... it is twitter bootstrap... it takes all the questions out for early design so you can focus on features. This is probably my main reason for going with it over react native. i'm also a huge fan of material-ui.com for web stuff... but i think flutter nails a more 'native' experience for mobile. I also like Dart as a language quite a bit. The flutter_graphql library works well. Integrated with firebase_auth for login. I'm using a qr scanner library that wraps the native stuff. Intellij support is quite good. Being able to hot reload on the device is awesome. No real complaints. =) pro-tip... one wart is their default state management. use the provider api instead. this should be the default imho.... examples... https://github.com/FilledStacks/flutter-tutorials/tree/master/014-provider-v3-updates https://github.com/FilledStacks/flutter-tutorials/tree/maste... https://www.filledstacks.com/post/flutter-architecture-my-provider-implementation-guide/ https://www.filledstacks.com/post/flutter-architecture-my-pr... https://github.com/rrousselGit/provider https://github.com/rrousselGit/provider