Uploaded November 2015 | Updated November 2026, 7 hours ago
When transition metal salts dissolve in solution, they produce free transition metal ions (or rather, aqua complexes) - when these ions encounter silicate ions, they form coloured precipitates of metal silicates.
However, the precipitation does not create a dense solid, but a semi-permeable membranous structure instead. These structures allow diffusion and osmosis to take place across them, resulting in a channel of precipitation that takes place upwards.
Procedure:
1 Pour sodium silicate solution into a container about one-third of the way through.
2 Add hot de-ionised water to this solution, stirring well with a glass rod, and dilute it in a ratio of 1:2
3 Allow the mixture to stand until the liquid is completely still.
4 Use a pair of forceps to drop one or two crystals of a transition metal salt of choice. Try to ensure that the crystals do not fall close to each other.
5 Cover the container with a piece of card and observe the silicates grow.
When transition metal salts dissolve in solution, they produce free transition metal ions (or rather, aqua complexes) - when these ions encounter silicate ions, they form coloured precipitates of metal silicates.
However, the precipitation does not create a dense solid, but a semi-permeable membranous structure instead. These structures allow diffusion and osmosis to take place across them, resulting in a channel of precipitation that takes place upwards.
Procedure:
1 Pour sodium silicate solution into a container about one-third of the way through.
2 Add hot de-ionised water to this solution, stirring well with a glass rod, and dilute it in a ratio of 1:2
3 Allow the mixture to stand until the liquid is completely still.
4 Use a pair of forceps to drop one or two crystals of a transition metal salt of choice. Try to ensure that the crystals do not fall close to each other.
5 Cover the container with a piece of card and observe the silicates grow.








![Applied AI Product Management: User Stories for an AI Feature
In this video, youll learn how to write effective user stories for AI-enabled apps—and why you should NOT be building chatbots everywhere.
What Youll Learn:
1. How to write user stories that embed AI into specific workflows
2. A new acceptance criteria format: Scenario-based writing
3. The Smart Breakdown feature example: Auto-generating subtasks from complex tasks
4. How to give LLMs clear instructions while maintaining control over your feature scope
Key Concept: Good AI Design ≠ Chatbots
Sloppy app design puts chatbots everywhere. Good AI design automates specific parts of your workflow seamlessly—users shouldnt even realize theyre interacting with AI.
The Scenario Format:
Given [initial condition]
When [user action]
Then [expected outcome]
This format gives you tighter control over what features the LLM builds, trading off some creativity for precision and reliability.
I built this for our public service community. If you find it useful, share it across the public service, please. And when you build something, tag me on LinkedIn (https://linkedin/in/yongkiat), and Id love to see what you create!
Lets grow together. See you in the videos!
Instagram: / rogue.teacher.sg
User Story:
On the to-do app page, I want to create a Smart Breakdown AI feature using Lovables inbuilt LLM integration with Gemini. Heres the user story:
As a user with a complex or overwhelming task, I want the AI to automatically break it down into smaller, actionable subtasks, so that I know exactly what steps to take and feel less overwhelmed by large projects.
Acceptance Criteria
Given I have created a new task with a title like Plan company retreat,
When I tap the ✨ Smart Breakdown button in the task detail view,
Then the AI should analyze the task and generate 5-10 relevant subtasks within 5 seconds.
Given the AI has generated subtasks,
When the generation is complete,
Then I should see a preview screen showing all suggested subtasks with checkboxes to select which ones to add.
Given I am viewing the suggested subtasks,
When I review the list,
Then each subtask should have a clear, actionable title and be ordered in a logical sequence.
Given the AI suggests subtasks with estimated timelines,
When my original task has a due date,
Then the subtasks should have suggested due dates distributed appropriately before the main deadline.
Given I am satisfied with the AI-generated subtasks,
When I tap Add All or Add Selected,
Then the chosen subtasks should be created under the parent task within 1 second and I should return to the task detail view.
Given I dont like some of the AI suggestions,
When I deselect certain subtasks before adding,
Then only my selected subtasks should be added to the task.
Given I want to make changes to a suggested subtask,
When I tap on a subtask in the preview,
Then I should be able to edit the title, due date, or other details before adding it.
Given the AI fails to generate subtasks (API error, timeout, etc.),
When the error occurs,
Then I should see a friendly error message: Couldnt generate breakdown. Please try again with a retry button. Applied AI Product Management: User Stories for an AI Feature](https://i.ytimg.com/vi/6o62X6G26Gw/mqdefault.jpg)

