Webflow has secured $76m in funding, are we going to see any improvements in your dev team?

You can, natively and quite easily on Webflow.
https://webflow.com/blog/how-to-build-breadcrumb-navigation-for-webflow-ecommerce

With tabs or some custom codes, you can do filtering and sorting as well.

PS. You cannot do this easily on Shopify.

1 Like

Breadcrumbs not related her (No way to create “real” 3 levels site tree URL). Mixitup and js are great for micro-filters (color or size) and do not solve site tree hierarchy issues.

“You cannot do this easily” - summarize my point :slight_smile:

1 Like

For the OP and anyone else interested in what’s coming next you can check out this Webflow article:
https://webflow.com/blog/what-weve-been-shipping-january-march-2020

Head towards the bottom to see what’s being released very soon :slight_smile:

12 Likes

Oh shit that’s a wonderful blog post!

3 Likes

Bingo. I prefer Webflow uses the same business model that 37 Signals used with the development of Basecamp. Build it with the understanding that it will not be for everyone and that is not a bad thing.

2 Likes

Except that that would be your responsibility right? If your client’s website doesn’t accomplish what they are looking for, who are they going to blame, you or webflow? It is the developer’s responsibility to know the tools of the trade.

whoooooosh

@Webflow Thx for the update :grinning:

2 Likes

Since no one created another post on the topic of whether Webflow should define themselves as a no code tool, I created one here: Is the "no code" branding, misleading?. I am going to delete my posts on the topic, so as not to hijack the original post. Other guys who shared opinions on this, please move them to that new thread, so that we respect the OP’s message.

Not sure if your background @anthonychan2509 is a developer… kinda guessing from this ranking. But, as someone who is “only” a designer, I wouldn’t even attempt to get into Wordpress or Drupal. So, it’s kinda apples to oranges. It [Webflow] literally is what Dreamweaver dreamed it could be (pun sadly intended).

Though, I do agree with your bullet points. And, especially on the last point. I think “design without coding” is still fundamentally false, and as you say purely marketing. It’s really “code by designing” - which, TBH, if you’re aiming for actual intelligent designers, should be more appealing as well as honest.

Their current how-to videos and general marking is I think setting up false expectations. If you can already handle Creative Suite, you should be ready as a designer to step up to Webflow. But, when they leave out some technical details, it just severely frustrates newcomers later on (to the extreme sometimes, in my own experience). If they would have made the video 6 min with more technical “why” and a touch more “how” in their videos, rather than all-to-easy 3 min vids, I think they’d have nailed things and set up the right expectations.

No one is going to beat Wix or Squarespace in the markets they’ve captured, and they shouldn’t waste time/money trying. After using Webflow, as a designer there is no way I’m giving up this level of control to go back to Squarespace, as easy as it is. Once you’ve had Webflow, Squarespace is a no go. When you are aiming to please studios with designers like Blind/The Futur… then, I’d say Webflow is going the right way.

5 Likes

oops, I should name that symbol drawing properly. lol

It is just my subjective feeling on the tools as a comparison.

It’s about how suitable the tools are for different types of users or projects, from “0” know nothing about coding even CSS :see_no_evil:, to “10” serious designer/developer/projects :space_invader:.

I am quite happy to see the Blog post mentioned by @Noah-R as I finally get some idea about what features are going to deliver soon and what are not. This is very helpful when you always have to prepare yourself for client’s question and have to make the best recommendation for clients.

( I am a designer, an elementary-level developer and an agency owner.)

SEO needs work for sure - og implementation is incomplete for FB and no twitter cards, manual static page canonical…

When WF release nested collections I’m going on an all night bender (edit … after this virus is sorted) :crazy_face:

5 Likes

I’m going to try and give an honest answer while remaining positive, I mean no offence to any humans or any software (be it Webflow or anything else!)

An interesting thread! In conclusion… Everyone LOVES Webflow (that’s why we’re all here right?) but maybe hates ‘bits’ of Webflow, which I get.

I get the Wishlist area seeming like nothing happens. I get the fact we’re paying customers. I get the marketing is awesome. I get there are some areas that are lacking.

My own six month experience using Webflow…

I’ve always longed for software where I could be in control. As a designer, I hate giving a design to a developer, waiting what seemed like ‘too long’ only to get something back that wasn’t ‘quite’ right. Maybe I was using rubbish developers, but I always wanted to be able to make changes myself rather than asking someone else to do it for me.

Webflow is awesome. There’s no doubt about it. It’s the first software I’ve tried that I’ve felt I can do 90% of everything that I wanted to do and with next to no developer help. All for what is actually quite minimal cost. I tend to build either really basic sites or fully-fledged ecommerce sites, so both ends of the spectrum.

For design, I can’t really fault Webflow. Where my frustration comes in (and there have been days of frustration) is reliability and missing basic features.

Reliability, well it is still fairly new, so I get there will always be some bugs, but I have been ‘stuck’ at times where things just wouldn’t load or everything is generally slow. It looks like it could be a cookie issue, but it’s not always ideal to clear your cookies multiple times a day.

As for missing basic features, thing like selecting more than one image at once from the gallery to delete, or uploading a 301 file so you don’t have to manually enter each redirect one-by-one. Perhaps I wrongly expected these to be features, but it meant having to find work arounds on what would have otherwise been a really simple issue.

But…

We’ve still been able to build an ecommerce site using Shopify for what it does best and Webflow for what it does best, a truly perfect match that has worked so well for us so far.

I’ve had no problems with support, I tend to get an email back the next day which is awesome.

And I do feel Webflow are listening - I mean was that blog post of new features always planned? Maybe, but it went online at a good time.

Webflow is…

  • An ice cream but with no sprinkles
  • A box of chocolates but with only one layer
  • A pizza but with pineapple you have to flick off…

Webflow is awesome, just with a ‘hint’ of disappointment in some areas.

Still, I am still using it, we are about to launch some very large sites on the platform after some experiments with smaller sites and I look forward to where the platform will be in the future :slight_smile:

3 Likes

I definitely interpreted that as a general nod to this discussion, which I think is admirable. Plenty of other companies would have locked the thread just based off the tone of the first message and that would have been that.

Anyways, nothing left for me to say in this thread that hasn’t already been beaten to death. Stay safe, ya’ll!

2 Likes

I’ve had no problems with support, I tend to get an email back the next day which is awesome.

Getting an email the next day is nothing spectacular for a high-priced service which repeatedly claims that it takes long to implement new features because they are pursuing quality. We get emails the next day and then what happens? This is the important point. It is quite common for Webflow to redirect you to the Wishlist, or this forum, and that is pretty lame.

But what is worse, is that support staff sometimes admit that there’s a bug in their system and then promise they’d report it to the dev team, and then guess what? Nothing gets done. Just browse the bug topics on this forum and pay attention to their posting dates.

At the end of the day, good support means quality code. You do not need a thousand people at support desks to simply give replies, you need a product which does not break so often, so that contacting support be a rare occasion on the first place!

And to those who mentor us how we should be grateful for the great efforts Webflow take to bring us this (once) great product, I’d like to say that Webflow should be grateful to us for taking time to report bugs, making screenshots, gifs, descriptions, communicating with support, doing everything to help a bug get resolved. We do not get paid for that time, but we do pay for Webflow!

And after all those efforts, we see nothing getting done. I stopped reporting bugs long ago, because that is wasting my time.

I definitely interpreted that as a general nod to this discussion, which I think is admirable. Plenty of other companies would have locked the thread just based off the tone of the first message and that would have been that.

*plenty of other mediocre companies

If Webflow repeatedly propagate that they are bringing us an awesome product and put quality first, then showing accountability is the least that they can do.

If they posted that blog announcement as a form of response to this thread, without anyone actually responding here, face to face, as it were, then they are cowards and certainly not great at their job.

1 Like

@PiXL3 is right. Webflow is providing the world’s most advanced code-free web editor, and they’re lightyears ahead of the competition. I’m personally very impressed with Webflow and their progress. With hundreds of thousands of users, there’s inevitably going to be a lot of feature requests. Webflow can spend the money on office parties for all I care. Their team obviously knows what’s best and how to create an amazing product. Keep up the good work Webflow!

2 Likes

I personally think as developers we have to use the tools we have that are available at the time and do the best we can for the particular project. You’re absolutely right that we can’t expect we flow to deliver a code free solution to every single possible eventuality in web dev, especially when web dev is changing by the day. As developers, we know that Webflow is just a starting point. Even hosting is incredibly expensive on this platform. Depending on the client and depending on the solution, Webflow should always be a place for developers to start and then use custom code to integrate the rest of the site, with custom CSS or JS. That’s literally why they give us Footer & Header custom fields.

Exactly. It’s a ‘no-code’ platform if you build with only the capabilities of Webflow. The problem with the web is it’s so much more expansive than the box that Webflow puts you in. That’s why I have always used Webflow as a starting point. It’s amazing for building and launching a test server for a client to see the functionality of the site. But then once you start adding more complex items like a better working CMS (CraftCMS or Wordpress), working with Google Maps API, or integrating JS in a more manageable way than the custom interactions Webflow provides. You inevitably have to write custom code or export the code and integrate it into a CMS. Honestly though, the $39 or whatever I pay for that monthly saves me the time and headache of writing the HTML and CSS from scratch.

1 Like

Symbols inside symbols and Nested Collections are huge!
Can’t wait for that!

I am not Webflow developer, but I believe :point_up_2: these are difficult.

It would be great if something much easier (I guess) but super helpful would come sooner. Such as:

It’s a feature that is somehow there but not yet to extend to RTE.

2020-04-02 9.54.31
It’s frustrating when blog clients complain about why they cannot change text color, etc.