14
Replies
I don't know what was meant by that comment from Nancy.
By @osgood_
==========
If you ask professional web developers which tools they used, GoLive, Muse, Dreamweaver and XD are not on their list. Although marketed at people who want to work with code, Dreamweaver is mainly used by amateurs, hobbyists and beginners who crave a visual design tool over a plain code editor.
XD is a visual design tool for UI/UX designers who can hand off to a separate team of experienced coders. Do those coders use Dreamweaver? Unlikely.
Thanks for replying all.
I guess webhosts with their website builders are the future for "amateurs" like me : )
By @davidhelp
Be careful. These webhosts are holding their clients to hostage. They can up their prices (see Bubble) at will and even close their servers down. Similarly, if their online program falls behind,, you do not have an alternative. At least, users of Dreamweaver do have alternatives.
Be careful. These webhosts are holding their clients to hostage. They can up their prices (see Bubble) at will and even close their servers down. Similarly, if their online program falls behind,, you do not have an alternative. At least, users of Dreamweaver do have alternatives.
By @BenPleysier
I guess that may be some what applicable to Wappler as well given the niche workflow it uses. It would be difficult for anyone without any or little coding knowledge to step away from it and get up to speed quickly with some other workflow. Putting all your eggs in one basket whether that be an editor or some server hosted application is always a risk.
So you think that if Wappler goes belly up today, that all if my Wappler sites are doomed? And you call yourself a professional, giving advice to people in a less fortunate situation?
By @BenPleysier
I never said anything about your website being doomed. More will you be doomed is the point or will your client be doomed.
If you can only create websites or apps using one specific editor then, yes, l would say you're doomed and probably have limited abilities which would impact on you significantly should even Wappler raise their prices beyond what you want to pay or can afford to pay, which is what you referred to in terms of Bubble. Wappler recently did raise their prices for new customers l believe and justifiably so given the extensive work which has gone into producing the app. However this move still upset some of the current users as they thought it applied to them.
As for saving 75% production time yes that's good if true but l doubt it unless your coding abilities are very limited but it's also self serving. I would be more concerned that the client could easily source an alternative developer to manage their website if they so chose to do so. I'm pretty sure that would be a difficult task for them given Wappler uses its own workflow which would not be common to the majority of developers.
I guess it's easy to become blinkered and self serving once you become dependent on specific processes as it presents a level of security that you wish not to lose.
Sorry, I am not married to Wappler. I use it to make my task easier. Even more importantly so, Wappler allows me to create a website at a much faster rate than most of the Dreamweaver alternatives that you quoted above. This is particularly important for my clients because it reduces the cost of development.
By @BenPleysier
It rather sounds as though you are married to Wappler with all due respect and being without it would severely impact on your ability to produce what you need to produce. Web-development IS morally corrupt, at all levels. I very much doubt you explain to your client your reasonings for using the workflow you do and the possible concequences as mentioned in my last post, let's not go over those again. It's not just unique to Wappler but to other worflows like React and Vue cli. Once you package something up and use the distribution files its almost impossibe, if not impossible for any other web developer to continue work on the project without the build files which are only available to the original developer. Sorry but I rather have issues with any workflow which 'locks' a client into a vendor, that is as I say morally corrupt.
I recently inherrited a site that was created in Webflow. Great program. The reason that the client came to me is because he could not find another developer who would tackle a Webflow project.
By @BenPleysier
Exactly my point and yet you do the same thing but using Wappler instead. Youre part of the problem.
Then there is the client with a great looking website created by an old fashioned hand coder. All working well with plenty of Javascripts, Stylesheets and PHP processes. The developer decided to retire and the client had a problem finding another developer. The code was to hard to understand.
By @BenPleysier
The code should never be too hard to understand, the developer wasnt knowledgable enough to understand it, that does happen. Granted, its not easy taking on anyone elses wesbite whaterever its build in but there is more of a chance if the website is written using main-stream coding, rather than coding which has never been documented.
The reason that I say this is because Wappler is not unique in producing code that may be hard for non-coders to understand. I am sure that you would have no problem with the source code driving App Connect.
By @BenPleysier
Wrong, I often look at the code of websites built using Wappler and I have zero idea a lot of the time of what the code means or does I'm afraid and I would class myself as reasonably knowledgable main-stream coder. I don't think I would be alone in that either!
Just one more. This client came to me with a static website using Bootstrap for styling. Admittedly, it was an older version of Bootstrap, but I immediately felt at home.
By @BenPleysier
Well Bootstrap is a main-stream workflow so even if you dont like Bootstrap you should be able to work with a website built in Bootstrap. As a professional web developer you would probably have had a lot of exposure to it, and its well documented, unlike maybe AppConnect.
We will for ever be arguing about workflows. Be assured, that there are many workflows out there, some of which I would never copy, others that I could live with.
By @BenPleysier
For sure. My voice is but a distant murmur but its what I'm passionate about, others not so much.
AdChoices