Futura - an app to store memories

Hello IC friends,
We (me and @552020 ) would like to present our small project, Futura, which is in early stage development, an app for long term preservation of digital memories.

We got a small grant just to test interest in different possible versions of the same idea through an ad campaign. The grant was not supposed to be for the actual development of the app. We are posting in the forum as part of the grant requirements, but also to get feedback.

The three verticals are:

  1. Family
    A long-term family memory vault to preserve, share, and pass down memories to loved ones and future generations.

2. Wedding
An album designed to capture and preserve a couple’s wedding memories. An emotional gift for newly weds

3. Transcendence
An AI-powered digital self, reconstructed from personal memories. Allowing future generations to interact with and “talk to” a preserved personality of a loved one. Because we thought people could host their biography or similar data in Family vertical, so Transcendance was the ambitious possible continuation.

The videos of the ad campaign are not the best ones but we were not able to leverage the marketing and creative support from Lunar Strategy. It was announced as part of the prize (“a PR campaign”) for our Taikai Hackathon win in October 2024, but it did unfortunately not materialize. As a result, creatives and targeting were developed and executed by us.

Even though the scope of the grant was just covering testing interest, we couldn’t help to develop an alpha version of the wedding vertical.

We worked on 2 repos: a frontend (having web2 backend features and access to web3) and backend one (web3 only).

The frontend one hosts a Juno branch (along with a separate development branch, including a Juno staging environment) that powers three dedicated landing pages—one for each vertical. As part of our grant requirements, we integrated Juno Analytics to track engagement and validate interest. Users can choose web2 or web3 storage.

ic.futura.now maps to Juno, the landing pages are for Fake Door testing
futura.now is web2 frontend with web3 features for hosting pictures

We also have to post a video here !

A big thanks to David for Juno, and for all the support and help along the way on Discord :raising_hands:. Also to Tiago for all the supports.

5 Likes

I have so many questions -

Can I ask who is awarding the grant? Has it already been awarded?


Regarding your ideas, could you explain them in the context of the problem(s) they’re solving?

so you’re selling immortality?

1 Like

Tiago is the mentor of Futura Now? The Portuguese hub was the event organizer for the hackathon, and Lunar Strategies is responsible for PR Marketing as a prize in the hackathon?

futura.now

  • Uploading images gives Error 403
    Apparently images are being rejected by Amazon S3 Web Server

ic.futura.now

  • There exist no option to upload images
  • Also authentication of users does not exist

I am a bit surprised the Futura team spent fourteen months building this project, and then after no code commits for several months decided to make a paid marketing campaigns although basic functionality was missing, broken pages, no authentication, no image upload?

Based on the findings and outcomes from this 30 dollar marketing campaign, and this presentation to collect funds, is Futura now fully committed to continuing development this app?

Example: Futura Clone Built in 9 Minutes:

This is an app created with AI in nine minutes using one prompt, the application is more complete because authentication works and image upload works.

2 Likes

to be fair, the fact that they have any website at all makes this project better qualified than half of the projects listed here:

It appears from that statement, they realized that they messed up and are fixing things… that’s good.

But you didn’t asked! Do so, I will try to answer :slightly_smiling_face:
But above all congrats for your 30 minutes clone, it does look amazing! Which platform have you used ?

ic.futura.now is mapped to Juno, which is Fake Door testing (scope of the grant)
Fake Door Testing means the “users” are somewhat expendables, they don’t get anything (no storing in our case)
Actual upload (both web2 and web3) is on futura.now - Sorry if that wasn’t clear in the original message!

Sure the Juno and not juno and various repo make it hard to understand. Juno was a grant requirements, it makes sense for Dfinity. While we really appreciate the work and all what the platform can offer we prefer a more hands on approach where one manages repos and backend as he wishes. So we did the grant on one side and our project on another side. We don’t believe in everything web3, we prefer web3 where it shines. But again, Juno and Davide’s work are amazing!

I am a bit surprised the Futura team spent fourteen months building this project, and then after no code commits for several months decided to make a paid marketing campaigns although basic functionality was missing, broken pages, no authentication, no image upload?

Such hostility, sorry again if this wasn’t clear in the original message:
Grant covers the fake door testing and campaigns - the repo have the milestones so you can check them out (In the docs, I think you’ll have access) and then you’ll have plenty of material for super self wondering and. even precise crictisising!

Most of the commit are for the web2 or web3 developments in the front or backend repo - not covered by the grant.
You can check the Juno branch and its staging if you just want to review our grant job.

I’m from France, are you ? Cause I feel right at home with this “Is that where my tax money is going” underline message - Fraternité brother!

I don’t know if I can share that, but to be honnest there isn’t much people.

The problem question is a great one, we’ll try to find back our research docs and write a correct answer in the following days. We have lots of it, including interviews (audio) where we tried to research interests people have with their memories and its digital form. We have so much of it that it’s tough to answer simply right away. The problems were mostly of psychological and social nature (sometimes we framed them as simple human needs). With the wedding vertical it was more tangible, mesureable, and occured often if you target professionals (photographers as instance) which is why we felt better about this vertical

Please go and find out then, and let us know when you know. There’s a good chap.

Then I don’t think you understand what you’re trying to deliver.

In particular you should be able to explain why what you’re trying to deliver should reside on-chain (which is expensive, and is likely to be the worst place for indefinite storage that requires continued payment of storage costs).

Thanks for taking the time to clarify and respond — I appreciate the additional context. I watched your full presentation, and I do want to say that you are a good presenter. :ok_hand: :100:

I understand that the presentation and marketing campaign were part of a grants process, and I accept that the campaign was not intended to reflect the full state of your production infrastructure. :handshake:

That said, my feedback is based partly on the same marketing data you referenced, as well as what was publicly visible at the time: the campaign execution, several repositories, and multiple live pages.

I don’t know Juno, I don’t know Davide, and I didn’t approach this through the lens of grant compliance — only through observed outcomes. Juno is some plug 'n play CMS hat generates backend code is my understanding.

From that perspective, I arrived at different conclusions.

When people (including myself) hear about a new AI startup, the natural reaction is to do due diligence. Seeing several frontends — many of them broken — creates poor optics. Regardless of scope or intent, this is the impression it leaves externally.

After all, you and your team in-between yourself have participated in more than 10 hackathons -
you should be more experienced then having to use Juno for user authentication.

The core issue for me isn’t whether milestones were technically met, but whether the campaign meaningfully benefited Dfinity and its stakeholders. A paid campaign that drives users into flows where they cannot meaningfully progress — due to missing or broken functionality — creates a perception problem, particularly when traffic appears concentrated around the team’s own geography.

Especially when the team does not seem committed to their cause.

When I read “it makes sense for Dfinity,” I struggle to reconcile that statement with what the data appears to show. From the outside, it’s difficult to see this as a clear win for the ecosystem or for those ultimately funding these initiatives. :thinking:

I want to be explicit about one thing: I am not accusing you or your team of fraud. If anything, I suspect there may be broader structural issues in how grants, marketing obligations, and incentives are designed — situations where teams are encouraged to run campaigns before products are truly ready, or where promised support does not fully materialize.

This is why some observers raise questions. For example:

  • If a professional PR or marketing campaign was part of winning a hackathon 14 months ago, people naturally wonder why the visual quality and UX appear inconsistent. You even partnered with a professional photographer and yet it looks like the images and graphics was created in a hurry using paint.

  • If technical mentorship was provided, it becomes difficult for outsiders to reconcile that with core functionality — such as image uploads — still not working after a long development timeline.

These aren’t accusations; they are questions driven by visible outcomes.

So when I ask whether I’m wrong — I genuinely think we may both be right. You are right about the scope and constraints of the grant. I may also be right about how this looks from the outside.

My original question was simple: why present this now, in this state, if the project is still evolving so significantly?

You cite a partnership with a wedding photographer in Berlin and describe a vision around ownership transfer using AI and blockchain. It’s an interesting space — but after spending significant time on due diligence, I still struggled to see a clear path toward profitability or execution consistency, which makes the public push harder to understand.

From the outside, the combination of a long build timeline, a public marketing campaign, and visible gaps in basic functionality creates a perception problem — one that can look like minimal interest is execution rather than genuine momentum, regardless of the internal reality.

Thanks again for engaging openly. I’m not hostile, and I would rather support your project than ignore it. I’m simply explaining why, from an external point of view, it has not yet come across as something clearly positioned to deliver on its promises. (Besides prize money there have been several grants as per my understanding.)

I also sense that perhaps there is some frustration from the team as well:

I am sure you have spent a lot of time on this, but if this is an incubated / accelerated project with funding, mentors and a web 3 marketing burau behind it, official partnerships, etc

I expected more, and that is why people are wondering, how much money went into this. Not just your grants, stipendiums and prize money, but also to people external to Futura who are paid by the community (Dfinity) to accelerate, market, and mentor Futura.

We are after all a community, we should support each other, not take advantage or go after each other!

So if you have some grievances and insights as well, which I suspect you do (?), you are most welcome to share here, and that will be the ultimate value that Futura (for now) can provide this community, Dfinity and its stakeholders.

What is really going on here?

1 Like

Hi everyone,

I appreciate the critical feedback and the discussion here. I’d like to provide some necessary context regarding the scope of this grant that was missing from the initial post.

This $5k grant was approved with a specific core condition: the team had to utilize Juno and its analytics capabilities to validate their project idea. The primary goal was to demonstrate to the community how Juno can be utilized in a live environment.

Regarding the results: While I understand the concerns regarding the existence of different deployments for this project, this grant was strictly focused on the Juno implementation. You can review the documented campaign and analytics results here:

Next Steps: I have spoken with @lmangall and @552020. They are preparing a comprehensive follow-up post that explicitly details their experience building on Juno. We hope this will provide transparency for the community and serve as valuable user feedback for @peterparker.

Best, Marco

2 Likes

Hello everyone,

thanks for all the feedback.

@marc0olo we specified also in the initial post that the grant was not for the development of the app itself but that it had a more limited scope, but maybe it was not clear enough. We wrote that “The grant was not supposed to be for the actual development of the app.” and “Even though the scope of the grant was just covering testing interest, we couldn’t help to develop an alpha version of the wedding vertical.” We are preparing an article about our experience working with Juno, which will be published soon.

The feedback by @DeFiAdventures, @WebTreeSoftwareSolut and @Lorimer was useful; thank you for that, and we are still working on addressing all the outlined issues. The 403 Problem should be fixed now, and we wrote an article explaining the product from a problem/solution perspective. It would be nice if you could give some feedback on it, and tell us it is understandable and if it answers at least some of the questions you had: Futura's Solution

Cheers,

Stefano

I’d recommend reviewing T&C’s

It looks like wedding-related services are currently visible and promoted to users from age 13 but in countries such as Portugal, France, and Germany the legal minimum age for marriage is 18.

1 Like