Tldr; Application Notes is the content category for in-depth, practical write-ups about real circuits you’ve designed. If your post gets accepted here, you’ll receive 100 € AISLER Store Credit and we may feature your work on our social channels and in our newsletter. This is a moderated category: every submission is reviewed by our team before it goes live.
What are Circuit Appnotes?
Circuit Appnotes are where you document how you actually built a circuit so that others can safely reuse your approach. If Community Tips are quick hints and Deep Dives are for learning, Circuit Appnotes are your place to say:
Here is the circuit I needed, here were the constraints, this is how I chose the components and here’s what you can copy.
Typical examples:
-
selecting ceramic capacitors for an LDO so it stays stable over lifetime,
-
designing a robust input filter for a switch-mode supply,
-
choosing current-sense resistors and amplifiers for a motor driver,
-
layout and component choices for a low-noise analogue front end.
A good Circuit Appnote feels like something that could sit next to a datasheet as an official design guide – just written by you, for the community. 
Use this category when:
-
you’ve solved a concrete circuit-level problem,
-
your solution is reusable for others,
-
and you’re willing to share not just the “what”, but also the “why”.
What should a Circuit Appnote contain?
You don’t have to be rigid, but strong Circuit Appnotes usually follow a similar flow.
Use your own style – the structure below is a guide:
1. Abstract
A short summary that answers:
-
What circuit or problem is this about?
-
Why does it matter?
-
What is the key outcome or recommendation?
Three to five sentences are enough.
2. Introduction – context for the circuit
Set the scene:
-
What does this circuit do in the bigger system?
-
What are the main requirements? (voltages, currents, environment, reliability, cost, size, etc.)
-
What can go wrong if it’s done poorly (instability, noise, component stress, field failures)?
3. Design considerations
List and explain the key parameters and constraints:
-
Electrical: voltage ranges, current limits, ripple, ESR windows, timing, stability.
-
Components: technology choice (e.g. X7R vs X5R), voltage rating, package, tolerance.
-
Layout / mechanical: track lengths, thermal paths, clearance, board size limitations.
-
Any relevant graphs or tables from datasheets (e.g. stability regions, derating curves).
This is where you show that you’ve actually read and interpreted the datasheets.
4. Real-world effects
Move beyond “ideal textbooks” and talk about real behaviour:
-
Derating effects (temperature, DC bias, ageing, tolerance, parasitics).
-
Interactions between parts (e.g. output capacitor and LDO control loop, inductor and switching node layout).
-
Measured quirks, pitfalls, or things you learnt the hard way.
If you use tools like manufacturer calculators or online platforms, you can briefly show screenshots or describe the relevant results.
5. Design example – step by step
This is the heart of your Circuit Appnote.
-
Start with concrete numbers:
input/output voltages, max current, ambient temperature, expected lifetime, etc. -
Show how you narrow down:
-
which topologies or parts you considered,
-
why you chose one over another,
-
how you picked values and ratings.
-
-
Apply derating and margins, and show worst-case thinking.
-
If useful, include: schematic snippets, small tables, measurement screenshots.
By the end, the reader should be able to follow your reasoning and replicate your design process with their own exact parts.
6. Recommendation & conclusion
Wrap up with a clear, practical summary:
-
Which components or configurations do you recommend, and why?
-
What margin do you have, and where are the most important trade-offs?
-
Are there obvious variants (cheaper, smaller, more robust) and when to use them?
7. Limitations & notes
Be open about the scope:
-
Which assumptions did you make (environment, usage, manufacturing tolerances)?
-
What should readers still check or validate in their own system?
-
Anything that is intentionally out of scope.
Moderation, rewards & timelines
The Circuit Appnote category is moderated.
That means:
-
Every submission is reviewed by our admin team before it becomes visible.
-
We check:
-
Does it fit the Circuit Appnote category?
-
Is it technically coherent and understandable?
-
Is it original (no copy-paste)?
-
Does it meet a basic quality level (structure, clarity)?
-
Rewards
-
If your post is accepted as a Circuit Appnote, you will receive 100 € AISLER Store Credit.
-
We aim to review all Circuit Appnotes within 5 working days.
-
If we have questions or need clarification, we will contact you within that time frame from: developer-relations@aisler.net
So if you see an email from that address, it’s us 
Originality, plagiarism & featuring your work
To keep things fair and valuable for everyone:
-
Plagiarism is not accepted.
-
Do not copy content from manufacturer appnotes, blogs, articles, or other community posts.
-
Do not submit content that you did not write or do not have the rights to use.
-
-
Short quotes from datasheets, standards or other sources are fine, as long as:
-
they are clearly marked as quotes,
-
and you reference the original source.
-
By submitting a Circuit Appnote, you confirm that:
-
the text, images and diagrams are your own work
(or that you have explicit permission to use them), and -
AISLER may:
-
publish your Circuit Appnote in the forum,
-
feature it on social media,
-
highlight it in newsletters or other communications, always with proper credit to you as the author.
-
If you’ve ever thought, “I’ve already solved this circuit properly once – others shouldn’t have to reinvent it from scratch”, then the Circuit Appnote category is exactly where that work belongs.
And now it comes with 100 € in Store Credit as a “thank you” on top.