Quick AI search on feasibility of having another app on our phone next to the one they force on us, that allows us to replace them all with an app of our own.
AI results
Ai vibe coding direct democracy project
1 vibecoding 5pm
Here are some of the most highly-rated “vibe coding” / low-code / AI-assisted development platforms in 2025, along with what makes them stand out and what trade-offs to watch. If you tell me what you mean by “vibe coding” exactly (just design prototyping? full apps? AI assistance?), I can tailor further, but this should give you a good map.
What people mean by “vibe coding”
“Vibe coding” seems to refer to platforms/tools that make the act of building software more enjoyable, fast, collaborative, often AI-assisted, minimal setup, good feedback loops, sometimes text-to‐app, prompt-driven, etc. It sits between no-code, low-code, and AI-native tools.
Top platforms & tools in 2025
Here are some of the front-runners, grouped by style/use case. I’ve included ratings, strengths, and limitations where information is available.
| Platform / Tool | What it is / Vibe features | What people like most | Limitations / Trade-offs |
| Cursor | AI-native code editor. Lets you write/modify code via plain language, works across file/project. Seen as one of the highest “vibe” tools. (All About AI) | Sleek, smart, good for developers who want AI help + control. High rating in “vibe” tool comparisons. (All About AI) | May still require manual tweaking, debugging; might have limitations for large complex apps; cost can grow with usage. |
| Replit & Replit Agent | Cloud IDE + multiplayer + AI assistants. Starts fast, minimal setup. (Fueler) | Great for prototyping / teams / learners; very accessible. Hosting + collaboration built in. (synergylabs.co) | Might not be as powerful or customizable for “production grade” apps; performance / scaling may be less flexible. |
| Lovable | Prompt-to-app platform aimed at non-technical founders. Clean UI, drag/drop or prompt interactions. (Open Data Science Conference) | Very intuitive; people who want something usable quickly without much setup tend to love it. (Medium) | Less control over low-level specifics; if you need complex logic or custom backend work, might hit ceilings. |
| Bolt.new | Fast prototyping via description; more flexibility than very simple tools. Good middle ground between pure AI prompt and more manual build. (Medium) | Speed; ability to get something live quickly; useful for MVPs. (Medium) | Feature set still catching up; stability / integrations might lag; costs for scale uncertain. |
| Base44 | AI-powered “liquid” full-stack app builder; includes backend, auth, database, deployment. (Fueler) | Very appealing when you want everything handled: UI + backend + infra. Good user feedback. (Fueler) | Might not allow deep customizations; if you outgrow it, migrating / scaling might be harder; pricing and ownership/licensing may be constraints. |
| OutSystems | More established enterprise low-code; visual modelling; strong compliance/security. (PeerSpot) | Enterprise readiness; support/SLAs; robust features, scalable. (clevr.com) | Can be expensive; more overhead; steeper learning curve; overkill for small/simple projects. |
| Mendix | Low-code enterprise / business apps; good visual modelling, collaboration, multi-cloud deployment. (clevr.com) | Very strong on reliability, integrations, ability to handle complexity. (clevr.com) | Less nimble for super fast prototyping; cost/licensing; dependency on platform constraints. |
| Microsoft Power Apps | Part of Microsoft’s ecosystem; good for internal tools / business apps; works well for organizations already invested in MS tooling. (PeerSpot) | Nice integration; familiar ecosystem for many; less technical barriers for users already in Microsoft stack. (PeerSpot) | Not always ideal for highly custom or public-facing apps; UI/design flexibility sometimes limited; vendor lock-in potential. |
What seems most “vibe-coding”-y vs what’s more “enterprise”
From reading reviews & user feedback:
- More vibe / more fun / more creativity: Cursor, Replit, Lovable, Bolt.new, Base44. These tend to emphasize speed, low friction, maybe prompt or natural language, prototyping, collaborative / sharing.
- More enterprise / heavier projects: OutSystems, Mendix, Power Apps. These give more structure, governance, security, but less of the lightweight “type a prompt and get something live fast” feel.
Trade-offs
Here are some of the things people are seeing as drawbacks or considerations:
- Advanced control & custom logic — The more you want deep integration, performance optimization, custom infrastructures, or nonstandard flows, the more likely you’ll hit limits in the lighter vibe tools.
- Scalability & stability — For full production, uptime/monitoring/security often better in established platforms.
- Pricing & ownership — AI or vibe-coded tools sometimes hide costs in “usage limits,” or make moving off the platform harder. Also check who owns generated code / data.
- Customize UX/design — The simplest tools sometimes force design or UX constraints; for more polish you may need to export or code-tweak.
Bottom line & suggestions
If I were you, here’s what I’d pick depending on your needs:
- Want to build something very fast for a demo / MVP / small side project: Base44, Lovable, or Bolt.new.
- Want something with more developer control but still very enjoyable: Cursor or Replit.
- Need enterprise-grade, long-term support: Mendix or OutSystems.
If you like, I can put together a ranked list of the top ~10 vibe coding platforms tailored for your stack (MySQL/Postgres vs NoSQL, mobile vs web vs dashboards), with pricing & demo links. Do you want me to do that?
2) 5:10 pm Are the UK acts of parliament past present and future accessible with an api, or would the content have to be collacted by screen-scraping from a government website
Excellent question — and one that comes up a lot among legal tech and civic-data developers in the UK.
Here’s a current (2025) overview of the available options for accessing UK Acts of Parliament (past, present, and upcoming) by API vs. scraping.
✅ 1. Official API: Legislation.gov.uk API
Yes — there is an official API.
The UK National Archives (TNA) provides one through legislation.gov.uk.
🔹 Features:
- Covers Acts of Parliament (primary legislation), secondary legislation, drafts, explanatory notes, and EU retained law.
- Returns data in XML or JSON via the Open Law API endpoints.
- Allows access to:
- Titles, years, and citations
- Full text of Acts
- Revisions (up-to-date vs. original versions)
- Hierarchical structure (parts, sections, schedules)
- Metadata (royal assent date, geographic extent, status, etc.)
🔹 Example endpoint:
Returns metadata and structure for the Data Protection and Digital Information Act 2023.
You can programmatically iterate through:
or by type (e.g., ukpga, uksi, etc.).
🔹 Formats available:
- XML (default)
- JSON
- RDF (linked data)
- HTML (human-readable)
🔹 Access:
- Public & free
- No registration or API key required
- Rate limits are unofficial but generous for responsible use
🔹 Docs:
See the National Archives’ official documentation:
👉 https://www.legislation.gov.uk/developer
⚙️ 2. Unofficial Wrappers & Libraries
A few open-source projects wrap the Legislation.gov.uk data into easier APIs:
- legislation.gov.uk-parser (Python) – scrapes & structures XML into JSON for legal NLP tasks.
- openlegis (Node.js) – a lightweight wrapper for accessing Acts and sections.
- UK-Legislation-API (community REST proxy) – wraps the TNA data into REST + pagination.
These can simplify connecting to apps or databases without manually parsing XML.
🧩 3. For “future” or “upcoming” Acts
This is trickier — future Acts (Bills) are not part of the Legislation.gov.uk API until they receive Royal Assent.
However:
- You can get Bills in progress and parliamentary stages from the UK Parliament API:
👉 https://members.parliament.uk/memberapi
and
👉 https://developer.parliament.uk/
That API includes:
- Bill summaries
- Stages in Commons/Lords
- Sponsors
- Associated documents (PDFs, explanatory notes, debates)
Combine both APIs for full coverage:
- Parliament API → Bills (proposed or in progress)
- Legislation.gov.uk API → Acts (enacted law)
🧠 4. Screen scraping
You don’t need to scrape Legislation.gov.uk unless:
- You need HTML presentation (e.g., formatted display identical to the site)
- Or you want to crawl Bills pre-publication (rare case)
Otherwise, API + feeds give all structured data cleanly.
🚀 Summary Table
| Source | Type | Data Access | Format | Covers | API Key | Notes |
| Legislation.gov.uk (TNA) | Acts, SI, amendments | ✅ API | XML, JSON, RDF | Enacted laws | ❌ | Official, best source |
| UK Parliament API | Bills, debates, MPs | ✅ API | JSON | Bills in progress | ✅ Free key | Great for “future” Acts |
| TheyWorkForYou / mySociety | MPs, speeches | ✅ API | JSON | Debates / context | ✅ Free key | Can link contextually |
| Scraping | Full HTML text | ⚠️ Possible but not needed | HTML | Formatting only | ❌ | Only if you need custom layout |
💡 Recommendation
If you want a full legal data pipeline:
- Pull Bills → from Parliament API
- Watch for Royal Assent
- Fetch Acts → from Legislation.gov.uk API
- Store structured data (JSON/XML) in your own DB for local search or AI summarization
- Optionally enrich with TheyWorkForYou for debates context
If you like, I can give you:
- Example Python code to fetch and parse Acts dynamically
- or a schema for storing them (Acts → Sections → Clauses → Amendments)
Would you like me to generate that next?
3) 5:12 Has anyone already been working on developing or prototyping a direct democracy app to replace representative democracy with a system where citizens directly approve or disapprove of legislation passing though UK parliament
Short answer: Yes — many people and organisations have prototyped and deployed direct-democracy / participatory-democracy platforms (and experiments in “liquid” or blockchain voting), but no credible, legal replacement of the UK’s representative Parliament exists — only pilots, civic platforms and civic-tech efforts. Replacing MPs with nationwide direct voting would require major constitutional change and solved problems far beyond software (identity, security, turnout, legal process, legislative drafting, royal assent, etc.).
Below is a compact overview with concrete examples, what’s been built, what’s been tested in practice, and the key legal/technical barriers.
What already exists (real projects / platforms)
- Decidim — a mature, open-source participatory-democracy platform used by cities and organisations to propose, debate and decide policies. It’s actively developed and used for real municipal participatory processes. (decidim.org)
- CONSUL — another widely-deployed open platform (originated in Madrid) for participatory budgeting, citizen proposals, debate and voting. Cities use it for local decision-making. (consuldemocracy.org)
- LiquidFeedback / Liquid Democracy toolkits — software and research used by parties and movements (notably Pirate Parties and civic groups) to experiment with delegable voting / “liquid democracy” models. (liquidfeedback.com)
- Blockchain / identity experiments — projects such as Democracy Earth have prototyped blockchain-based sovereign identity + voting systems aimed at global direct-voting models. These are experimental and controversial. (democracy.earth)
- Direct-democracy apps & small projects — there are apps and civic initiatives that let people propose and vote on referenda outside the state system (e.g., DirectDemocracy apps on stores). These are grassroots rather than statutory. (Apple)
UK-specific reality
- The UK already offers digital civic input channels (the official petitions site and Parliament’s systems), and UK civic tech groups (e.g., mySociety and others) work on better democratic data and engagement — but these are supplementary, not replacements for parliamentary procedure. The official petitions site and parliamentary processes remain the legal route for national law. (Petitions – UK Government and Parliament)
Pilots vs full replacement
- Pilots & municipal use: Decidim/Consul are used by local governments for participatory budgeting, proposals and consultations. That demonstrates the viability of digital participation at municipal scale. (decidim.org)
- National replacement? Not yet. No country has fully replaced representative legislatures with an app. Experiments (liquid voting, blockchain referenda) exist, but none are accepted as legitimate substitutes for a sovereign parliament in major democracies.
Principal obstacles (why an “app to replace MPs” hasn’t happened)
- Legal & constitutional constraints: Primary legislation, parliamentary privilege, the role of MPs, and Royal Assent are constitutional matters. Changing that requires law and political consensus, not only software.
- Identity & eligibility: Secure, fraud-resistant digital ID that meets democratic legitimacy and privacy norms is unsolved at national scale (risk of coercion, botting, duplicate accounts).
- Security & secrecy of the ballot: Secure end-to-end verifiable voting at national scale is a hard cryptographic and systems problem; many designs trade off secrecy, verifiability, or coercion resistance.
- Inclusion & digital divide: Ensuring equal access and avoiding disenfranchisement of non-digital populations.
- Legislative complexity & deliberation: Parliamentary scrutiny, redrafting, committee work and delegated legislation are complex — simple yes/no votes risk poor lawmaking.
- Political legitimacy & governance: Who controls the platform? How are disputes handled? How do you prevent misinformation or capture?
(These obstacles are why most nations use digital tools for consultation, petitions, or deliberative processes rather than wholesale replacement.)
Where the conversation / experimentation is heading
- Hybrid models: e.g., citizens’ assemblies, digital deliberation tools plus representative ratification, or more direct referenda for specific issues rather than full replacement. Tools like Decidim/Consul are heavily used for that. (decidim.org)
- Liquid-delegation experiments: groups trial dynamic delegation (delegate your vote to experts/trustees for issues you don’t follow). These are often party-level pilots. (liquidfeedback.com)
- Identity + verifiable voting R&D: blockchain and advanced cryptographic voting schemes are actively prototyped (e.g., Democracy Earth and other research projects), but they remain experimental. (democracy.earth)
Quick recommendations if you want to experiment / prototype
- Start at municipal scale — use Decidim or Consul to prototype participatory lawmaking on local issues (these are production-ready and open source). (decidim.org)
- Pair digital voting with deliberation — add forums, experts, and citizens’ assemblies to avoid “populist yes/no” problems.
- Pilot liquid delegation for a closed community (e.g., a city, association or party) before broader rollouts — that limits legal exposure. (liquidfeedback.com)
- Plan for identity & accessibility — design for inclusion, offline/offboard ways to authenticate and vote, and independent audits.
- Engage legal counsel & Parliament stakeholders early — if you imagine national law being affected, you’ll need legal pathways and political buy-in.
Want me to do one of the following next?
- Map 10 real projects (Decidim, Consul, LiquidFeedback, Democracy Earth, DirectDemocracy apps, plus UK civic initiatives) with links and short notes.
- Draft a practical pilot plan (tech stack, security, identity, legal sign-offs) suitable for a UK town council using Decidim/Consul.
- Produce a short threat & risk checklist for a national direct-voting app (security, legal, social risks).
Pick one and I’ll build it out right here.