When comparing Spark vs N2O, the Slant community recommends N2O for most people. In the question“What are the best backend web frameworks?” N2O is ranked 29th while Spark is ranked 41st.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Custom quick swipe features
Pro Free
Pro Robust customization options
Pro Syncs across devices
Pro Unified inbox
Pro Free snooze options
Pro Fast binary data
Pro Binary encoding and protocols
Here is a list of types of endpoints which are supported by EMQ and accesible to N2O apps: WebSockets, MQTT, MQTT-SN, TCP, UDP, CoAP. Normal use of N2O as a Web Framework or a Web Application Server is through WebSockets, but for IoT and MQTT applications it could be served through UDP or SCTP protocols providing application level message delivery consistency.
Cons
Con Horrible privacy policy
- Sends statistical data to several services known for bad privacy policies (Google, Facebook), also there's no way to opt out.
- Automatically creates an acount with the first address entered and subscribes you to their newsletter.
- Stores credentials for your email accounts on their servers.
- Stores your emails on their servers to push them to your devices.
- Server infrastructure seems to be located in the US.
Con Doesn't support many services
Many services such as Spam filters, Pocket, and other apps are not supported.
Con Doesn't show the counts of emails next to the folders
- On the Mac platform will show +999 for the folder that contains more than 1000 emails.
- On the iPhone, the platform will not show the counts next to the folder unless they are new emails.
Con Unfriendly developer community
Developers are often rude and unfriendly to users.
Con Bad documentation
It has bad documentation, which leaves out crucial steps, making it hard to learn.
