15 More Spectacular Sinks & Strange Wash Basin Designs
Wash this space… for some of the slickest sinks around! Designers have thrown out everything INCLUDING the kitchen sink in order to reinvent one of society’s most utilitarian fixtures. Turning on the creative faucet gives “brain drain” a whole new meaning – as illustrated by these 15 sink-ly spectacular washbasins!
(images via: Doornob and HighTech Design)
From Germany’s HighTech Design comes the Ammonite Washbasin. Composed of formed concrete, this sink is no 97 pound weakling… though it DOES weigh 97 pounds. Taking the Ammonite Washbasin for a “spin9rdquo; must be a unique experience and, if one isn’t careful, a dizzying one at that!
(images via: HighTech Design)
The Ammonite Washbasin comes integrated with a concrete slab countertop ranging from 900mm (36 inches) to 1190 mm (47.5 inches) and makes an excellent place to wash up after a meal of brontosaurus ribs. Amirite? Ammonite!
(images via: Idea X Idea)
Which came first, the sink or the Starship Enterprise? It’s a chicken & egg conundrum that would even befuddle Scotty – if he wasn’t busy wondering why the warp drive is running hot & cold.
(images via: Nippon Style and Pink Tentacle)
When Tetsuya Nakamura of Nippon Style set out to create the ultimate suite of bathroom fixtures, price was no object. He hopes you’ll feel the same way: his Premium Unit sinks are priced at 1.5 million yen ($13,000) each.
(image via: Pink Tentacle)
Nakamura’s Premium Unit tub goes for a cool 3 million yen ($26,000) and, as it’s more about form than function, purchasers are advised they “should enter the tub at their own risk, as the artist and dealer assume no responsibility for injuries or accidents that may occur.”
(images via: Amin Design and Trendir)
Amin Design has gone out on a limb – or a wing, at least – with its Swan Vessel sink. Unlike many sinks and washbasins, Bouchti Amin’s Swan Vessels feature custom chromed faucets integrated into the overall design,
(image via: Archzine)
Amin answers the chicken/egg question with the Eggy Sink, though many will remain confused. The Eggy Sink, like the Swan Vessel sink, includes unique polished chrome hardware.
(images via: Finest Fixtures and Gran-Selecto)
The Art Ceram Bathroom Sink, Wall Mounted combines the light and airy grace of modern Italian design with the spirit of the Space Age. The Urbinati-designed sink features a transparent basin and an invisible drain. Though eminently practical, it’s hard to imagine washing your socks in this exquisite sink.
(images via: Disegno Ceramica)
Disegno Ceramica has introduced a line of sinks and bathroom fixtures that show off a playful form while making no sacrifices when it comes to function. Most attractive is the Splash Collection comprising a shower base, wall hanging wash basin and a pedestal sink. Three colors plus white are available.
(images via: Disegno Ceramica)
Disegno Ceramica features other intriguing sink and fixture designs but none have the arresting appeal of the Splash Collection, where you can lighten up while you wash up.
(images via: Nova 68 and Trendir)
The Flo Pedestal Sink & Faucet was designed by Patrick Messier to be a free-standing fixture that looks great from any angle. The brushed stainless steel pedestal and chromed stainless & brass faucet riser give the impression of an early 20th century city tenement complete with fire escapes. The 19-inch deep sink is made of Perspex acrylic resin. The sink has but one moving part: the insulated faucet that also acts as a control for the water’s flow and temperature.
(images via: The Design Blog and Bornrich)
The Fat Sink is made of wood… not the optimal choice of material for a washbasin, one might think, but designer Tolga Baydar has no worries – how long have rainforests been around, after all? Sculpted of fine-grained wood and complemented by polished stainless steel fittings, the Fat Sink is a wo0oden wonder the likes of which haven’t been seen since the Spruce Goose took to the air.
(images via: Tuvie)
Is a portable sink all wet? Not necessarily. Jessica Nebel has engineered a sink that sits on top of a base… until you need to move it somewhere else. The drain holes match up when in sink mode and close when shifting watery loads to a kitchen island, patio or wherever the cook’s fancy takes them.
(images via: JAVIVI)
It’s hard to find any information about the above sink, other than it looks Japanese as it resembles some types of sake-drinking flasks and cups. The sink features many Kanji characters on both its inner and outer surfaces that just might translate to… “You missed a spot!”
(image via: Archiexpo)
The Elkay Mystic River Sink demands a lot of counter space but that’s just fine – you’ll need a lot of room for the crowd of admirers hoping to see this unusual, hand-crafted sink in action. Available in a number of finishes over 16 gauge stainless steel, the Mystic River Sink sports a bowl that slopes “downstream9rdquo; from faucet to delta, er, drain.
(image via: DesigneRoof and Native Trails)
The Luna sink from Native Trails is made of 16-gauge, hand-hammered copper finished in natural, antique and tempered finishes. For a brighter look, brushed nickel is also available. The stunning sweep of the 38-inch long basin may look odd, but the broad crescent is actually easier to use when preparing meals as kitchen scraps are swept right in.
(image via: DesigneRoof and Native Trails)
One of the advantages of copper sinks is that it has natural anti-bacterial qualities. Dangerous E Coli germs that can survive for weeks in the microscopic scratches of a brushed stainless steel sink are killed within mere hours in a copper sink.
(images via: Manolohome)
The “Profile9trade; 5 with Integrated Hand Basin by Caroma looks like a weird Japanese toilet, acts like a weird Japanese toilet, yet it hails from (of all places) Australia. The Profile is a green toilet… well, it’s white, but it’s green. After one flushes, the tank is filled from the faucet mounted atop the tank. Scrub up while you can – it’s not a huge tank and you don’t want to be caught short. Would a tolet like the Profile work in the USA? Perhaps… but before worrying about hand-washing how about remembering to flush?
(images via: Trendir and West One Bathrooms)
Time to take your hand-washing to a higher plane? Well all aboard, the Onda Washplane is here to sink all your previous conceptions of what a sink should look like.
(image via: Furnishism)
One of a series of Washplanes from Omvivo, the Onda Washplane looks like a liquid disaster waiting to happen but is in fact precisely engineered to direct water down the drain using only the force of gravity. Choose from glass or Corian, single or double.
(image via: Just Cool Design)
Well OK, bar ONE… the Canali modular faucet that doubles as a towel bar, thus killing two birds with one stone. It’s also the perfect place to wash up after you’ve been out killing birds with stones, since your towels will be nice and warm from running the hot water for a while.
Now that you’ve gotten in sink with sinks, take a look around your own home. Satisfied with your kitchen, bathroom and laundry room wash basins? Thought so… but making a change is easier than you think and as one can see, there are some amazing sink designs out there, most of which won’t see your money go down the drain.
See More in Design (or: Fixtures & Interiors)
7 Beautiful Modern Bathtubs and Bathroom Collections
Showers, bathtubs, etc., are no longer plumbing fixtures. They are pieces of beautifully designed and carefully crafted furniture that aren’t just meant to be utilitarian, they are meant to .
Strange & Clever Toilets: 14 of the Best Seats in the House
When asked to list essential, life-enhancing furniture around the home, there are not many people who would include their toilet. However, remove it from their home and they’d be aware of it in a .
Hip Potty Musts: 15 Concept Designer Toilet Brushes
From the outhouse to the White House, the best toilet brushes never bristle when it comes to cleaning the latrine. Combining carefully engineered ergonomics and sometimes surprising style to .
Swiss-Army Bathroom: Spine-Inspired Space-Saving Design
Like a giant-sized Swiss Army knife, this narrow column unfolds to reveal everything your bathroom could need — a NASA-worthy, space-age modular design idea. A water-transmitting ‘spinal .
Home Room: Plug-and-Play Modules Make Instant Living Spaces
Resembling a house turned inside out, the Cubitat is a hybrid architectural and interior design prototype designed to be a modular all-in-one solution that can turn any empty space into your new .
The text output stream sink backend is the most generic backend provided by the library out of the box. The backend is implemented in the basic_text_ostream_backend class template ( text_ostream_backend and wtext_ostream_backend convenience typedefs provided for narrow and wide character support). It supports formatting log records into strings and putting into one or several streams. Each attached stream gets the same result of formatting, so if you need to format log records differently for different streams, you will need to create several sinks — each with its own formatter.
The backend also provides a feature that may come useful when debugging your application. With the auto_flush method one can tell the sink to automatically flush the buffers of all attached streams after each log record is written. This will, of course, degrade logging performance, but in case of an application crash there is a good chance that last log records will not be lost.
Although it is possible to write logs into files with the text stream backend the library also offers a special sink backend with an extended set of features suitable for file-based logging. The features include:
- Log file rotation based on file size and/or time
- Flexible log file naming
- Placing the rotated files into a special location in the file system
- Deleting the oldest files in order to free more space on the file system
File rotation is implemented by the sink backend itself. The file name pattern and rotation thresholds can be specified when the text_file_backend backend is constructed.
file name pattern
rotate the file upon reaching 5 MiB size.
. or every day, at noon, whichever comes first
The file size at rotation can be imprecise. The implementation counts the number of characters written to the file, but the underlying API can introduce additional auxiliary data, which would increase the log file’s actual size on disk. For instance, it is well known that Windows and DOS operating systems have a special treatment with regard to new-line characters. Each new-line character is written as a two byte sequence 0x0D 0x0A instead of a single 0x0A. Other platform-specific character translations are also known.
The time-based rotation is not limited by only time points. There are following options available out of the box:
- Time point rotations: rotation_at_time_point class. This kind of rotation takes place whenever the specified time point is reached. The following variants are available:
- Every day rotation, at the specified time. This is what was presented in the code snippet above:
- Rotation on the specified day of every week, at the specified time. For instance, this will make file rotation to happen every Tuesday, at midnight: in case of midnight, the time can be omitted:
- Rotation on the specified day of each month, at the specified time. For example, this is how to rotate files on the 1-st of every month: like with weekdays, midnight is implied:
If none of the above applies, one can specify his own predicate for time-based rotation. The predicate should take no arguments and return bool (the true value indicates that the rotation should take place). The predicate will be called for every log record being written to the file.
The log file rotation takes place on an attempt to write a new log record to the file. Thus the time-based rotation is not a strict threshold, either. The rotation will take place as soon as the library detects that the rotation should have happened.
The file name pattern may contain a number of wildcards, like the one you can see in the example above. Supported placeholders are:
- Current date and time components. The placeholders conform to the ones specified by Boost.DateTime library.
- File counter ( % N ) with an optional width specification in the printf -like format. The file counter will always be decimal, zero filled to the specified width.
- A percent sign ( %% ).
A few quick examples:
Although all Boost.DateTime format specifiers will work, there are restrictions on some of them, if you intend to scan for old log files. This functionality is discussed in the next section.
The sink backend allows hooking into the file rotation process in order to perform pre- and post-rotation actions. This can be useful to maintain log file validity by writing headers and footers. For example, this is how we could modify the init_logging function in order to write logs into XML files:
the resulting file name pattern
rotation size, in characters
the log message has to be decorated, if it contains special characters
Finally, the sink backend also supports the auto-flush feature, like the text stream backend does.
After being closed, the rotated files can be collected. In order to do so one has to set up a file collector by specifying the target directory where to collect the rotated files and, optionally, size thresholds. For example, we can modify the init_logging function to place rotated files into a distinct directory and limit total size of the files. Let’s assume the following function is called by init_logging with the constructed sink:
the target directory
maximum total size of the stored files, in bytes
minimum free space on the drive, in bytes
The max_size and min_free_space parameters are optional, the corresponding threshold will not be taken into account if the parameter is not specified.
One can create multiple file sink backends that collect files into the same target directory. In this case the most strict thresholds are combined for this target directory. The files from this directory will be erased without regard for which sink backend wrote it, i.e. in the strict chronological order.
The collector does not resolve log file name clashes between different sink backends, so if the clash occurs the behavior is undefined, in general. Depending on the circumstances, the files may overwrite each other or the operation may fail entirely.
The file collector provides another useful feature. Suppose you ran your application 5 times and you have 5 log files in the «logs» directory. The file sink backend and file collector provide a scan_for_files method that searches the target directory for these files and takes them into account. So, if it comes to deleting files, these files are not forgotten. What’s more, if the file name pattern in the backend involves a file counter, scanning for older files allows updating the counter to the most recent value. Here is the final version of our init_logging function:
There are two methods of file scanning: the scan that involves file name matching with the file name pattern (the default) and the scan that assumes that all files in the target directory are log files. The former applies certain restrictions on the placeholders that can be used within the file name pattern, in particular only file counter placeholder and these placeholders of Boost.DateTime are supported: % y , % Y , % m , % d , % H , % M , % S , % f . The latter scanning method, in its turn, has its own drawback: it does not allow updating the file counter in the backend. It is also considered to be more dangerous as it may result in unintended file deletion, so be cautious. The all-files scanning method can be enabled by passing it as an additional parameter to the scan_for_files call:
While the text stream and file backends are aimed to store all log records into a single file/stream, this backend serves a different purpose. Assume we have a banking request processing application and we want logs related to every single request to be placed into a separate file. If we can associate some attribute with the request identity then the text_multifile_backend backend is the way to go.
You can see we used a regular formatter in order to specify file naming pattern. Now, every log record with a distinct value of the «RequestID» attribute will be stored in a separate file, no matter how many different requests are being processed by the application concurrently. You can also find the multiple_files example in the library distribution, which shows a similar technique to separate logs generated by different threads of the application.
If using formatters is not appropriate for some reason, you can provide your own file name composer. The composer is a mere function object that accepts a log record as a single argument and returns a value of the text_multifile_backend :: path_type type.
The multi-file backend has no knowledge of whether a particular file is going to be used or not. That is, if a log record has been written into file A, the library cannot tell whether there will be more records that fit into the file A or not. This makes it impossible to implement file rotation and removing unused files to free space on the file system. The user will have to implement such functionality himself.
The syslog backend, as comes from its name, provides support for the syslog API that is available on virtually any UNIX-like platform. On Windows there exists at least one public implementation of the syslog client API. However, in order to provide maximum flexibibity and better portability the library offers built-in support for the syslog protocol described in RFC 3164. Thus on Windows only the built-in implementation is supported, while on UNIX-like systems both built-in and system API based implementations are supported.
The backend is implemented in the syslog_backend class. The backend supports formatting log records, and therefore requires thread synchronization in the frontend. The backend also supports severity level translation from the application-specific values to the syslog-defined values. This is achieved with an additional function object, level mapper, that receives a set of attribute values of each log record and returns the appropriate syslog level value. This value is used by the backend to construct the final priority value of the syslog record. The other component of the syslog priority value, the facility, is constant for each backend object and can be specified in the backend constructor arguments.
Level mappers can be written by library users to translate the application log levels to the syslog levels in the best way. However, the library provides two mappers that would fit this need in obvious cases. The direct_severity_mapping class template provides a way to directly map values of some integral attribute to syslog levels, without any value conversion. The custom_severity_mapping class template adds some flexibility and allows to map arbitrary values of some attribute to syslog levels.
Anyway, one example is better than a thousand words.
the logging facility
the native syslog API should be used
the logging facility
the built-in socket-based implementation should be used
Please note that all syslog constants, as well as level extractors, are declared within a nested namespace syslog . The library will not accept (and does not declare in the backend interface) native syslog constants, which are macros, actually.
Also note that the backend will default to the built-in implementation and user logging facility, if the corresponding constructor parameters are not specified.
The set_target_address method will also accept DNS names, which it will resolve to the actual IP address. This featue, however, is not available in single threaded builds.
Windows debugger output backend
Windows API has an interesting feature: a process, being run under a debugger, is able to emit messages that will be intercepted and displayed in the debugger window. For example, if an application is run under the Visual Studio IDE it is able to write debug messages to the IDE window. The basic_debug_output_backend backend provides a simple way of emitting such messages. Additionally, in order to optimize application performance, a special filter is available that checks whether the application is being run under a debugger. Like many other sink backends, this backend also supports setting a formatter in order to compose the message text.
The usage is quite simple and straightforward:
Note that the sink backend is templated on the character type. This type defines the Windows API version that is used to emit messages. Also, debug_output_backend and wdebug_output_backend convenience typedefs are provided.
Windows operating system provides a special API for publishing events related to application execution. A wide range of applications, including Windows components, use this facility to provide the user with all essential information about computer health in a single place — an event log. There can be more than one event log. However, typically all user-space applications use the common Application log. Records from different applications or their parts can be selected from the log by a record source name. Event logs can be read with a standard utility, an Event Viewer, that comes with Windows.
Although it looks very tempting, the API is quite complicated and intrusive, which makes it difficult to support. The application is required to provide a dynamic library with special resources that describe all events the application supports. This library must be registered in the Windows registry, which pins its location in the file system. The Event Viewer uses this registration to find the resources and compose and display messages. The positive feature of this approach is that since event resources can describe events differently for different languages, it allows the application to support event internationalization in a quite transparent manner: the application simply provides event identifiers and non-localizable event parameters to the API, and it does the rest of the work.
In order to support both the simplistic approach «it just works» and the more elaborate event composition, including internationalization support, the library provides two sink backends that work with event log API.
The basic_simple_event_log_backend backend is intended to encapsulate as much of the event log API as possible, leaving interface and usage model very similar to other sink backends. It contains all resources that are needed for the Event Viewer to function properly, and registers the Boost.Log library in the Windows registry in order to populate itself as the container of these resources.
The library must be built as a dynamic library in order to use this backend flawlessly. Otherwise event description resources are not linked into the executable, and the Event Viewer is not able to display events properly.
The only thing user has to do to add Windows event log support to his application is to provide event source and log names (which are optional and can be automatically suggested by the library), set up an appropriate filter, formatter and event severity mapping.
Having done that, all logging records that pass to the sink will be formatted the same way they are in the other sinks. The formatted message will be displayed in the Event Viewer as the event description.
The basic_event_log_backend allows more detailed control over the logging API, but requires considerably more scaffolding during initialization and usage.
First, the user has to build his own library with the event resources (the process is described in MSDN). As a part of this process one has to create a message file that describes all events. For the sake of example, let’s assume the following contents were used as the message file:
After compiling the resource library, the path to this library must be provided to the sink backend constructor, among other parameters used with the simple backend. The path may contain placeholders that will be expanded with the appropriate environment variables.
Like the simple backend, basic_event_log_backend will register itself in the Windows registry, which will enable the Event Viewer to display the emitted events.
Next, the user will have to provide the mapping between the application logging attributes and event identifiers. These identifiers were provided in the message compiler output as a result of compiling the message file. One can use basic_event_composer and one of the event ID mappings, like in the following example:
As you can see, one can use regular formatters to specify which attributes will be inserted instead of placeholders in the final event message. Aside from that, one can specify mappings of attribute values to event types and categories. Suppose our application has the following severity levels:
Then these levels can be mapped onto the values in the message description file:
As of Windows NT 6 (Vista, Server 2008) it is not needed to specify event type mappings. This information is available in the message definition resources and need not be duplicated in the API call.
Now that initialization is done, the sink can be registered into the core.
In order to emit events it is convenient to create a set of functions that will accept all needed parameters for the corresponding events and announce that the event has occurred.
Now you are able to call these helper functions to emit events. The complete code from this section is available in the event_log example in the library distribution.
My earring fell down the sink drain.
Remove the P-trap under the sink. It's called a P-trap because it's sort of shaped like a P lying on its face, but it's where the pipe comes down, bends up, then bends over to go out through the wall. The bent part can be removed and if your earring is pretty heavy and you didn't have a tremendous flow of water going through there, you might be in luck.
Some mouth breather thumbed me down, disregard that. I'm giving good advice and I'm going to thumb-up everybody else who had a useful thing to say. You're not an idiot and this is an easy job to do, you could have your earring back and develop a little bit of experience and self-confidence, all for the price of a single pair of pliers. Get cracking and see how you do.
I purchased a new bathroom sink and faucet and set everything up according to instructions. The faucet instructions told me to use silicone for the drain lip (the border thing around the stopper in the bottom of the inside of the sink, flange?).
Anyways, underneath where the pipe comes out is a rubber gasket and I’ve used the plastic screw on the drain pipe to seal the gasket against the underside of the sink, but when I put a little bit of water in it, some water leaks out from between the gasket and the sink. I’ve tried tightening it as much as I can and it still leaks.
Should I be putting silicone or plumbers putty between the gasket and the sink? If possible, I’d like to avoid taking the drain lip off because I’ve already sealed it there. What should I do?
Here is a picture of the underside of the sink:
UPDATE: It turns out (haha) that the problem was that the rubber «washer» was actually threaded itself. I’m not sure if they are always like this, but I didn’t realize that it was threaded when I was assembling everything. So I assume that what was happening originally is that when I didn’t have the rubber washer close enough to the basin when I started tightening the nut (blue) that it was moving the the threads out of alignment or something and not making a good seal. Once I turned the washer a few turns upwards, then tightened the blue nut, it made a proper seal. All without using a bunch of putter or silicone.
UPDATE2: So it has been 10 months and it hasn’t leaked. Problem solved.
Thinking about the BLANCO SILGRANIT Sink?
A few months ago on my facebook page , I asked the question: “What is your kitchen sink preference? double or single”? These were the results:
When it comes to kitchen sinks, I’ve always owned the typical stainless steel double bowl sink. Like many love-hate relationships, I had my fair share of ups and downs with my previous owned sinks.
Here’s the thing. According to my husband, me washing the dishes is like Shamu the whale passing through the kitchen. I will admit—I’m a messy girl at the sink.
I’m one of those people who prefer to use a dishwasher any chance I get. However, every now and then, I get stuck hand washing big pots, baking trays and non-stick pans that I just can’t put in the dishwasher. . .and here is where my nickname “Shamu” comes into play. For the life of me, I could never figure out how to wash an oversized baking tray in a double bowl sink without getting water all over the countertops, the floors and the cabinets.
Being in our new house and having the creative freedom to pick our kitchen from scratch has made me the happiest girl ever. It was the perfect opportunity to address all the problems I ever had in the past, specifically my issues with the kitchen sink.
After much thought, I chose to go with the BLANCO SILGRANIT PRECIS CASCADE undermount sink (in cinder). This stylish single bowl is by far one of the best decisions I made for this kitchen! I always recommend doing your due diligence for any big item your about to purchase for your home. After all you want to ensure you’ll love if for years to come.
When it came to BLANCO SILGRANIT sinks, I did A LOT of research, I read A LOT of reviews and by the end of it, I confirmed that this was the sink for me.
Before, I get into the nitty gritty of this sink’s features, let me quickly sum up why I chose this model. The first obvious reason is because I can fit my baking trays in the sink without making a gigantic mess in my kitchen. Two, it’s low maintenance and extremely durable. And three, its freaking stylish and dresses up my IKEA kitchen!
When you look at this sink, you can automatically tell right off the bat that this is superior in quality and construction. The SILGRANIT is a rock-hard composite material, formed using 80% pure granite. It has a soft dull finish, which comes in a variety of colours.
The durability is supposed to be one of the best. So far it has stood up to my clumsiness (you know, the accidental dropping of wet pots and pans) and still not a single scratch! The SILGRANIT is also made to withstand heat up to 280ºC (536ºF). I constantly dump hot pots of water worrying that somehow it may damage or fade the interior of the sink but I’m proven wrong every time, it remains unaffected.
This sink has a depth of 8″. I wanted a deep bowl but not overly deep. Working with a small kitchen I wanted to be able to utilize the space under my sink. With an 8″ depth (&-1/4″ if you factor in the undermount), I was still able to clear a sliding garbage and recycling bin underneath the sink, which was high on my priority list.
The sink is deep enough to wash bulky items, however, the most brilliant part of the design is the secondary bowl with the stainless steel mesh basket (which is included with this sink by the way).
This has a depth of 5 -1/2″, which is a back-friendly depth for rinsing food or small items. Furthermore, I love the cascading effect of the water trickling down to the drain. Very clever!
This sink is obviously a work of art. It’s a key piece to the overall look and feel of our kitchen. The colour Cinder is a warm charcoal grey which looks stunning against our white quartz countertops. A colour combo that will stand the test of time!
The dimensions of the PRECIS CASCADE model are 28-3/4″ x 18-1/8″ which fits a minimum base cabinet of 33″. However, our installer was able to make it work on a 30″ IKEA base cabinet (always check with your installer first). Shape definitely matters when it comes to sinks. You get more volume when you have a rectangular shape, straight sides and a flat bottom. Soft rounded corners allow for easy cleaning and good drainage as well.
I personally love the undermount, I think it adds to the sleek look of this sink. Also it allows countertop crumbs to be easily swept into the bowl.
There’s no denying this is a good-looking sink. However, if I had to nit pick about the design, the only thing I would love to see in the future is a sleeker looking drain to match the contemporary look of the sink. I find the current drain to be a bit on the traditional side for the SILGRANIT sinks.
With that being said, they do have these neat CapFlow Strainer Covers that can be purchase. It just kicks everything up a notch!
This cover does not sit flush with the bottom of the sink so water is able to freely flow underneath when the tap is running. I do, however, find myself removing it sometimes when I’m washing big pots to get a flat surface.
I absolutely love my faucet! This single lever model with pull out spout is the BLANCOCULINA Mini in Stainless Steel. My favourite feature is probably the magnetized hand spray holder, which also has the dual spray toggle button. It has a 360° swivel and a flexible spring spout that reaches all four corners of this sink.
The soap dispenser is the BLANCO TORRE style in Stainless Steel finish. The shape and design complements the faucet perfectly. I was using another soap dispenser for a while and recently replaced it with the TORRE for a better match to my faucet. As soon as I started using it, I instantly felt a difference in quality (this is made of solid brass).
I have been using this sink for a few months now and maintenance has been next to nothing. To be honest, half the time I forget to even wash it down because the colour absolutely hides everything. I love the fact that this sink is non porous which means dirt and bacteria cannot penetrate the surface.
I have this very bad habit of emptying my coffee cup in the sink without turning on the water. Usually, marks are left where the coffee has dried up but once I run the water (which is many hours later) the stain literally washes away without scrubbing. I’m not even joking.
When I do clean the sink I just use dish soap and water. Usually a good reminder that I need to clean my sink is when a slight build up eventually forms around the stainless steel drain and/or the stainless steel is discoloured (usually from the staining of my coffee). This is as bad as it gets for me.
Again, a little soap and water does the trick. BLANCO does sell cleaners specifically for these sinks, however; I have yet to try them out.
Would I recommend this sink? Definitely!
Would I consider using it again in my future kitchen? Heck yes!
After living with my own SILGRANIT sink, I can see why people love them so much. It definitely meets every high expectation that I had.
Will this sink stand the test of time? With a lifetime warranty, I have no doubt whatsoever! Maybe I’ll post an update in a few years and let you know how it’s holding up
Now who still prefers a double bowl sink!?
Disclosure: I’ve always been a fan of BLANCO products so I was beyond psyched that BLANCO Canada has agreed to partner with me in my kitchen makeover. This post reflects my honest thoughts and opinions of the sink, faucet and soap dispenser. I was not compensated nor asked to write this review.