<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>BLE interface design advices</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/125924/ble-interface-design-advices</link><description>Hi, 
 We are defining a BLE interface for our product, choosing SIG and custom services, and while working on BLE for years now, I have still questions on how to design the BLE interface; like: 
 
 How many characteristics per service should we respect</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 01 Dec 2025 14:36:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/125924/ble-interface-design-advices" /><item><title>RE: BLE interface design advices</title><link>https://devzone.nordicsemi.com/thread/555888?ContentTypeID=1</link><pubDate>Mon, 01 Dec 2025 14:36:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:781b0a39-84e2-4980-b423-f450bf974c4b</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;There is no practical limitation on the number of characteristics, this is more about organizing the service(s) in a logical way. This is particularly important for the standard services defined by the SIG that are used in all kinds of different products, but for your custom services you can choose whichever makes most sense for you and your application. More characteristics will add overhead and memory usage though, so I would try to keep the number of characteristics within reasonable limits.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>