u/PressureOutside

Hi! I’m preparing Duuo for release on Google Play and need Android users for a 14-day closed test.

Duuo helps accountability partners set goals, share check-ins, message each other and track progress together.

Testers will need to:.

1. Join using the Google Play opt-in link I’ll send.
2. Install Duuo and remain opted in for at least 14 days.
3. Try the onboarding, goals, partner invitations, messages and check-ins.
4. Send me any bugs or usability feedback.

How to Join

1. Join the Group: https://groups.google.com/g/duuo-android-testers
2. Become a tester: https://play.google.com/apps/testing/com.duuo.app
3. Install Duuo: https://play.google.com/store/apps/details?id=com.duuo.app

I’m happy to test your Android app in return. Please comment or DM me if interested thank you!

Honestly didn't know you have to go alot of this - from an iOS Engineer

Hi! I’m preparing Duuo for release on Google Play and need Android users for a 14-day closed test.

Duuo helps accountability partners set goals, share check-ins, message each other and track progress together.

Testers will need to:

1. DM me the Gmail/Google-account email used on their Android device.
2. Join using the Google Play opt-in link I’ll send.
3. Install Duuo and remain opted in for at least 14 days.
4. Try the onboarding, goals, partner invitations, messages and check-ins.
5. Send me any bugs or usability feedback.

I’m happy to test your Android app in return. Please comment or DM me if interested—thank you!

First of all god speed to everyone building.

So there was a time I posted here about me starting a micro-SaaS (getrisiti.com) and some dudes were like do you even understand the meaning of a SaaS and what goes with it yada yada. Instead I converted that bad energy into positive energy and I continued building my micro-SaaS anyways.

I want to announce today, however much we haven’t launched we have got two big companies on our waitlist and one awaiting a scheduled demo call on Monday, and about 437 businesses on direct consumer app waitlist

One is the biggest bus ticketing platform and the other is the biggest seed and seedling company established in 1929.

Don’t listen to words of shiet, use them as your biggest motivator.

We’re building Risiti: API infrastructure for Kenyan software platforms that need to add KRA eTIMS invoicing to their products.

We’re designing it for developers building:

• POS systems
• ERPs and accounting software
• Ecommerce platforms
• Garage and pharmacy management systems
• Vertical SaaS products
• Marketplaces serving multiple businesses

Risiti is not a replacement for your product’s dashboard or customer experience.

Your team builds the interface and workflows that suit your users. Risiti handles the underlying eTIMS infrastructure: merchant onboarding, item registration, invoicing, credit notes, purchases, stock movements, asynchronous KRA submission, retries, and compliance status.

The API is designed for secure, server-side integration and supports platforms managing multiple merchant businesses.

We’re now looking for developers to test the sandbox and challenge the architecture before we expand production access.

We would especially value feedback on:

• Resource and endpoint design
• Multi-tenant merchant isolation
• Authentication, API-key scopes, and rotation
• Idempotency and concurrent requests
• Invoice sequencing
• Asynchronous processing and KRA downtime
• Webhook delivery, retries, and signature verification
• Error codes and recovery instructions
• Failed-submission handling
• Branch-level configuration
• Sandbox realism
• Documentation quality

Questions we want answered:

• Which endpoints feel awkward or badly designed?
• Which fields are confusing, unnecessary, or missing?
• Which real-world eTIMS workflows have we overlooked?
• What would make integration difficult in an existing POS, ERP, marketplace, or SaaS product?
• What would stop you from trusting the API in production?
• Are we exposing too much eTIMS complexity—or abstracting too much of it away?

Explore the API reference and test the sandbox:

developers.getrisiti.com

You do not need to adopt a Risiti merchant interface. Integrate the API into your backend and build the experience your customers need.

Direct, technical criticism is welcome. We would rather uncover weak assumptions now than after businesses depend on them.

overview of risiti developer docs and reference

I’ll respond to questions here and share the improvements we make from your feedback.

Disclosure: I am the developer of DashPaper.

DashPaper is a macOS app that lets you run desktop widgets built with HTML, CSS, and JavaScript.

Website: https://www.dashpaper.app

Product Hunt: https://www.producthunt.com/products/dashpaper

Problem

I wanted my Mac desktop to be more useful without turning every small tool into a full desktop app.

The desktop is always there, but most of the time it is just wallpaper or scattered windows. Apple widgets are useful, but they are limited if you want to build your own small tools, dashboards, clipboard helpers, timers, score widgets, or personal workflows.

DashPaper is my attempt at making the desktop programmable.

It lets you run small widgets that feel at home on macOS, but are built like tiny web apps using HTML, CSS, and JavaScript.

Current example widgets include in first release:

- Notes

- Daily Quote

- Pomodoro

- Clipboard

- Weather

- World Cup 2026

- Custom/community widgets

Comparison

Compared to Apple’s built-in macOS widgets:

Apple widgets are polished and integrated, but they are not really designed as an open playground for quick custom widgets. DashPaper is more open. The goal is to let developers and power users build small desktop tools with normal web technologies.

Compared to tools like Übersicht and similar desktop-widget apps:

Those tools are very flexible, but DashPaper is trying to be more approachable and more productized. I want it to have polished built-in widgets, a simple widget manager, and a community-widget system where a widget can be shared as a small HTML/CSS/JS folder.

So the direction is:

- More open than Apple widgets

- More polished and beginner-friendly than raw desktop scripting

- Lightweight enough for small everyday tools

- Simple enough for web developers to build widgets quickly

Pricing

DashPaper will always be free.

Download: https://www.dashpaper.app

What I would love feedback on

1. Would you keep desktop widgets visible during the day, or do you prefer a clean desktop?
2. What widget would actually be useful enough to live on your Mac desktop?
3. Would you install community widgets if they were simple HTML/CSS/JS folders?
4. Does this feel more useful for normal Mac users, developers, or both?

Thanks. I would genuinely appreciate blunt feedback from Mac users here.

Short Demo Video of Dashpaper user enabling a world cup widget.

https://reddit.com/link/1u7fsv5/video/4sqo95airn7h1/player

I’m experimenting with a macOS desktop setup where the widgets are just tiny HTML/CSS/JS projects.

The app I’m building is called DashPaper. It gives the widgets a native desktop shell, then each widget handles its own UI and logic.

So instead of a full app for a timer, notes, currency converter, clipboard, or little API dashboard, you can have tiny desktop widgets that feel like programmable sticky notes.

I’m mainly trying to figure out the right balance between useful and cluttered.

For people who customize their desktops:

What widget would be worth permanent desktop space?

I’m working on DashPaper a desktop widget app where every widget is just HTML/CSS/JS.

The whole idea came from something that annoyed me:

Why does every tiny utility become a full-blown app?

A timer becomes an app.
A notes card becomes an app.
A currency converter becomes an app.
A dashboard becomes another dashboard.

DashPaper is my attempt at making those things tiny again.

Small widgets.
On your desktop.
Built like mini web pages.
Shared like little tools.

Examples I’m testing:

• Pomodoro
• notes
• clipboard
• quote widget
• World Cup mini widget
• tiny personal dashboards

Already ships with the widgets above

I’m curious from people here:

What widget would make you install something like this?

Could be very boring. Actually boring is probably better.

NOTE: Widgets can be community built and submitted here: https://github.com/buchabarn/dashpaper-widgets for private widgets, drag and drop your widget folder into the widgets folder opened when you click add widget in the app

https://reddit.com/link/1u7dtfb/video/9qe6zw95en7h1/player

For my tech nerds who would like to know the stack and a few details about the native runtime:

Tooling and Language: Objective-C, Swift, C++, Webkit, CMake, NPM
Downloadable Size: 2MB
Unarchived Size: 2.2MB

IMO most big SaaS are sleeping on ai search optimization and as a solo dev, that’s where you tap. You create a micro-saas and heavily optimize for ai searches, it’s the next frontier and whoever does it first has a big advantage.

I haven’t launched yet but take me as an example. My micro-saas Risiti is always recommended by the big LLMs ChatGPT, Grok, Claude, Perplexity whenever someone searches about eTIMs invoicing app for SMEs Freelancers and the rest and it’s always ranked highly as a good alternative to eTIMs official app.

I have dominated a keyword on Google, and I don’t even have a clue how I did, it might be pure lucky or codex is good at SEO. FYI it manages all my SEO.

If you google risiti, I will always show up first. KRA that has much authority regarding such keywords has been dethroned, now I am coming for eTIMS

https://preview.redd.it/e2eor5wkmpxg1.png?width=2388&format=png&auto=webp&s=a09eff3141881ab4f332c18ac7d684752729851e