4 ms·

People, I´m a copywriter for around 6+ years. I´ve built what we can call MVP up on the link in 3 hours and now I am creating the software. The software needs s

People, I´m a copywriter for around 6+ years. I´ve built what we can call MVP up on the link in 3 hours and now I am creating the software. The software needs storage space with each user having his own, active tasks, language selection and scheduler for an easy first version. I want it on the web after somebody buys service. Question on hand: I know how to code some basic front-end and learning back-end but I want to use no-code tools since they seem easier. Can I use Bildr, Webflow or Bubble with Airtable and if so, is it going to work correctly?

js4ever 4y ago
No, it will be a joke, limited, slow, sub-par experience, expensive at scale, not attractive for users ... It's a fast way to trash your idea
- PatrikSlachta 4y ago
  What tech stack would you use? I´m kinda´ new and last time I learned was in school with Python, HTML, CSS and stuff
  - js4ever 4y ago
    Nothing wrong with that stack, you will be in full control. Personally I prefer something like react or vue for the frontend and node.js for the backend. The great thing about it it's all in JavaScript so really only 1 language. But it's a matter of preference, I recommend you to use the stack you feel more comfortable with.
  - globalise83 4y ago
    For MVP type stuff, Meteor JS is still a good option since you don't waste time building a login system etc. and can develop your business logic instead.
- PatrikSlachta 4y ago
  Altough I am thinking Ruby would be both quick and easier to release
  - js4ever 4y ago
    Ruby is good as well, but if you have zero knowledge about it and plan to start from scratch... Maybe not, it's harder to find dev working on it compared to other stacks (python, JavaScript, Go, ... Even C# is more popular)
    - PatrikSlachta 4y ago
      Okay, thank you a lot and since I am yet a solo-founder, do you think you could provide me with useful links that could help me build this because I am a rather untalented creature. :D
      - js4ever 4y ago
        YW, sure please check this: https://github.com/gothinkster/realworld https://github.com/gothinkster/realworld It's a collection of 100 implementation of the same project but in different languages. This might help you to choose your preferred stack and see a real world example on how to use them and learn
- kristiandupont 4y ago
  There are domains where user experience is vital. Consumer apps that serve as nothing but entertainment, or fields with fierce competition for instance. And then there are domains where there is a problem that isn't solved or solved well. I don't know anything about the market for copy writing, so I can't say whether this falls into one or the other but if it's the latter, starting out with no-code is a completely rational approach.
- malux85 4y ago
  Yea I think the main, major problem with no-code tools is that they are not as composable as real coding. How that manifests is in a “difficulty cliff” - everything is very easy until that one thing that you absolutely need - it’s impossible - and since the components aren’t infinitely malleable there’s nothing you can do about it. What happens if you launch and that impossible thing is something critical that your biggest, paid, customer wants? A close number 2 is the janki-ness, and then the rest of the things you mentioned
  - enos_feedler 4y ago
    A related problem is they say you can export to real code and have infinite flexibility, but now the tool and the code are out of sync. The tooling doesn’t have a handle on this new code.
ojkelly 4y ago
Despite the attitude of some of the other comments, the code and stack are less important than you’d think. If you can create an MVP with no-code tool, yeah it might be janky but it might also let you prove out your idea with paying customers with the smallest time and money investment. Over time developing the software in house gives you control over the roadmap of features, and generally let’s you deliver a better experience. Unless you want to hone your engineering skills and use this as nice side project to do so, you’re probably well served playing to your strengths and working on getting customers. You’ll hit a wall with no code software at some point, that’s where you can sprinkle in some custom code. No code is just someone else’s saas api at the end of the day. If you trust the service, and they have an API that does what you need it to, don’t get bogged down in it. Maybe in the future you build the whole thing in custom code, but if you’ve got enough functionality to charge money for, the next question (at least from the lean startup approach) is to validate it with paying customers. Good luck!
- realitysballs 4y ago
  Well said!

js4ever 4y ago

No, it will be a joke, limited, slow, sub-par experience, expensive at scale, not attractive for users ... It's a fast way to trash your idea

PatrikSlachta 4y ago
What tech stack would you use? I´m kinda´ new and last time I learned was in school with Python, HTML, CSS and stuff
- js4ever 4y ago
  Nothing wrong with that stack, you will be in full control. Personally I prefer something like react or vue for the frontend and node.js for the backend. The great thing about it it's all in JavaScript so really only 1 language. But it's a matter of preference, I recommend you to use the stack you feel more comfortable with.
- globalise83 4y ago
  For MVP type stuff, Meteor JS is still a good option since you don't waste time building a login system etc. and can develop your business logic instead.
PatrikSlachta 4y ago
Altough I am thinking Ruby would be both quick and easier to release
- js4ever 4y ago
  Ruby is good as well, but if you have zero knowledge about it and plan to start from scratch... Maybe not, it's harder to find dev working on it compared to other stacks (python, JavaScript, Go, ... Even C# is more popular)
  - PatrikSlachta 4y ago
    Okay, thank you a lot and since I am yet a solo-founder, do you think you could provide me with useful links that could help me build this because I am a rather untalented creature. :D
    - js4ever 4y ago
      YW, sure please check this: https://github.com/gothinkster/realworld https://github.com/gothinkster/realworld It's a collection of 100 implementation of the same project but in different languages. This might help you to choose your preferred stack and see a real world example on how to use them and learn
kristiandupont 4y ago
There are domains where user experience is vital. Consumer apps that serve as nothing but entertainment, or fields with fierce competition for instance. And then there are domains where there is a problem that isn't solved or solved well. I don't know anything about the market for copy writing, so I can't say whether this falls into one or the other but if it's the latter, starting out with no-code is a completely rational approach.
malux85 4y ago
Yea I think the main, major problem with no-code tools is that they are not as composable as real coding. How that manifests is in a “difficulty cliff” - everything is very easy until that one thing that you absolutely need - it’s impossible - and since the components aren’t infinitely malleable there’s nothing you can do about it. What happens if you launch and that impossible thing is something critical that your biggest, paid, customer wants? A close number 2 is the janki-ness, and then the rest of the things you mentioned
- enos_feedler 4y ago
  A related problem is they say you can export to real code and have infinite flexibility, but now the tool and the code are out of sync. The tooling doesn’t have a handle on this new code.

ojkelly 4y ago

Despite the attitude of some of the other comments, the code and stack are less important than you’d think. If you can create an MVP with no-code tool, yeah it might be janky but it might also let you prove out your idea with paying customers with the smallest time and money investment. Over time developing the software in house gives you control over the roadmap of features, and generally let’s you deliver a better experience. Unless you want to hone your engineering skills and use this as nice side project to do so, you’re probably well served playing to your strengths and working on getting customers. You’ll hit a wall with no code software at some point, that’s where you can sprinkle in some custom code. No code is just someone else’s saas api at the end of the day. If you trust the service, and they have an API that does what you need it to, don’t get bogged down in it. Maybe in the future you build the whole thing in custom code, but if you’ve got enough functionality to charge money for, the next question (at least from the lean startup approach) is to validate it with paying customers. Good luck!

realitysballs 4y ago
Well said!